CVE-2016-20072: BBS e-Franchise WordPress Plugin SQL Injection – Remote Data Exfiltration Risk
A critical security flaw exists in the BBS e-Franchise 1.1.1 WordPress plugin that allows attackers to steal sensitive data directly from your WordPress database without needing to log in. The vulnerability is in how the plugin handles the `uid` parameter—attackers can inject malicious SQL commands that trick the database into revealing user accounts, passwords, and other sensitive information. This is a classic SQL injection attack delivered through web requests to pages using the plugin's shortcode functionality.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 8.2 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- Weaknesses (CWE)
- CWE-89
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
BBS e-Franchise 1.1.1 plugin for WordPress contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the uid parameter. Attackers can craft requests to pages using the plugin's shortcode with UNION-based SQL injection in the uid parameter to extract sensitive data from the WordPress database including user information and taxonomy terms.
4 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2016-20072 is an unauthenticated SQL injection vulnerability (CWE-89) in BBS e-Franchise 1.1.1 for WordPress. The plugin fails to sanitize user input in the `uid` parameter before passing it to SQL queries. Attackers can construct UNION-based SQL injection payloads through shortcode-enabled pages to execute arbitrary SQL, bypassing authentication entirely. The attack surface is wide since no login is required and the malicious parameter is processed through publicly accessible shortcodes.
Business impact
Exploitation enables attackers to exfiltrate sensitive user data including credentials, email addresses, and customer information from your WordPress database. Depending on your site's content, attackers may also access taxonomy terms and custom post metadata. This exposure creates risk of account takeover, identity theft, regulatory compliance violations (GDPR, PCI-DSS), reputational damage, and secondary attacks using stolen credentials across your infrastructure. The high CVSS score (8.2) reflects the ease of exploitation and severity of confidentiality impact.
Affected systems
Any WordPress installation running the BBS e-Franchise plugin version 1.1.1 is vulnerable. The flaw affects all sites using this plugin regardless of WordPress version, provided the plugin's shortcodes are active or accessible. Multi-site WordPress installations and WooCommerce stores using this plugin for franchise management are especially at risk if they process sensitive customer or user data.
Exploitability
This vulnerability is highly exploitable. It requires no authentication, no user interaction, and minimal technical complexity—attackers need only craft a malicious HTTP request with a SQL injection payload in the `uid` parameter to a page where the plugin's shortcode is present. Automated scanning and exploitation tools can readily identify and attack vulnerable instances. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms network accessibility, low attack complexity, and zero privilege/interaction requirements.
Remediation
Immediately disable or remove the BBS e-Franchise 1.1.1 plugin from all WordPress installations. Contact the plugin vendor to determine if a patched version is available; if not, evaluate alternative franchise management plugins with security certifications. Do not re-enable the plugin until a vendor patch is confirmed and applied. Verify the update applies to version 1.1.1 specifically before deployment to production.
Patch guidance
Check the BBS e-Franchise plugin repository or vendor website for an updated version that addresses SQL injection in the `uid` parameter. Apply patches only from the official vendor or WordPress.org plugin directory. Test the patched version in a staging environment first, particularly shortcode rendering and any franchise lookup functionality. After patching, audit database logs for signs of prior exploitation. If no patch is forthcoming, permanently deactivate and remove the plugin.
Detection guidance
Monitor web server logs and WordPress access logs for requests containing SQL injection patterns in the `uid` parameter (look for keywords: UNION, SELECT, OR, --, /*, and encoded variants). Implement database query logging to identify unusual SELECT queries extracting user_login, user_email, or other sensitive columns. Use WordPress security plugins with WAF capabilities to block requests with SQL syntax in shortcode parameters. Review database access logs for timestamps correlating to any suspicious HTTP activity.
Why prioritize this
This vulnerability merits immediate patching due to its high CVSS score (8.2), lack of authentication requirement, ease of exploitation, and direct exposure of sensitive user data. The attack can be automated and deployed at scale. However, it is not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, suggesting active in-the-wild exploitation may not yet be widespread—though that does not reduce the urgency of remediation given the trivial exploitation complexity.
Risk score, explained
The CVSS 3.1 score of 8.2 (HIGH) reflects: network-based attack vector (AV:N), low attack complexity requiring no special conditions (AC:L), no privileges or user interaction needed (PR:N, UI:N), confidentiality impact (C:H) from direct data exfiltration, and minimal integrity impact (I:L) from potential database modification. The unchanged scope (S:U) and lack of availability impact (A:N) prevent a critical rating, but the ease of exploitation and high sensitivity of exposed data justify the HIGH severity.
Frequently asked questions
Can this vulnerability be exploited remotely without touching our server?
Yes. Attackers only need to send HTTP requests to pages where the plugin's shortcode is active. No shell access, no plugin installation by the attacker, and no physical access is needed. A single malicious request can extract your entire user database.
If we update WordPress, does that fix this vulnerability?
No. This is a plugin vulnerability, not a WordPress core issue. Updating WordPress does nothing to address SQL injection in the BBS e-Franchise plugin. You must update or remove the plugin itself. Verify any security patch from the plugin vendor.
How can we tell if we were already attacked?
Check your WordPress debug log (wp-content/debug.log) and database query logs for unusual SELECT statements extracting sensitive columns. Web server access logs should show requests with SQL keywords in the `uid` parameter. A security audit or forensic review by specialists is recommended if you suspect prior exploitation.
What data is at highest risk?
User login names, email addresses, password hashes, and any custom user metadata stored in the WordPress database are directly accessible. If your site integrates WooCommerce or other plugins, order data, customer addresses, and payment information may also be exposed depending on database schema.
This vulnerability intelligence is provided for informational purposes to support security decision-making. SEC.co does not provide legal, compliance, or liability advice. Organizations are responsible for verifying patch availability and compatibility with their specific WordPress and plugin configurations before deployment. Security testing should only be performed on systems you own or have explicit permission to test. Timelines and availability of vendor patches are not guaranteed; alternative mitigation or decommissioning of the plugin may be necessary. Consult your security team and vendors directly for guidance specific to your environment. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20062HIGHSQL Injection in Simply Poll 1.4.1 WordPress Plugin - Unauthenticated Data Theft
- CVE-2016-20063HIGHSQL Injection in Single Personal Message 1.0.3 – Credential & Data Theft Risk
- CVE-2016-20065HIGHUnauthenticated SQL Injection in Product Catalog 8 WordPress Plugin
- CVE-2016-20068HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20069HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20071HIGHCritical SQL Injection in WordPress 404 Redirection Manager Plugin v1.0
- CVE-2016-20073HIGHSQL Injection in Answer My Question 1.3 WordPress Plugin
- CVE-2017-20243HIGHWordPress Car Park Booking Plugin SQL Injection Vulnerability