Security readout for executives and security teams
Plain-English summary
WP Bannerize plugin versions 2.0.0 through 4.0.2 can let an authenticated attacker read sensitive database information through SQL injection. This is a data exposure risk for WordPress sites using the plugin. The provided sources do not show CISA KEV listing or confirmed active exploitation.
Executive priority
Prioritize remediation for public or customer-facing WordPress sites, especially where many users have accounts. The main business risk is confidential data exposure from the site database. Urgency is high, but sources do not support calling it actively exploited.
Technical view
CVE-2021-39351 is an authenticated SQL injection flaw in WP Bannerize, tied to the id parameter in Classes/wpBannerizeAdmin.php. CVSS 3.1 is 7.7 with low attack complexity, required privileges, no user interaction, changed scope, and high confidentiality impact.
Likely exposure
Exposed assets are WordPress sites running WP Bannerize versions 2.0.0 through 4.0.2. An attacker needs authenticated access; the provided bundle does not specify the minimum WordPress role or capability required.
Exploitation context
The sources describe possible sensitive information exfiltration, but do not provide evidence of active exploitation. KEV status is false in the bundle. Treat this as a credible authenticated data exposure issue, not a confirmed in-the-wild campaign.
Researcher notes
Evidence names the vulnerable parameter and file location, but does not specify the minimum role, fixed version, or exploit telemetry. Validate exposure through version inventory, role access review, and vendor advisory follow-up rather than assuming exploitation or a particular patch level.
Mitigation direction
- Inventory WordPress sites for WP Bannerize installations and versions.
- Disable WP Bannerize on affected sites until vendor guidance confirms a safe version.
- Restrict WordPress account access to trusted users only.
- Review Wordfence and WordPress plugin guidance for remediation details.
- Back up affected sites before plugin removal or replacement.
Validation and detection
- Confirm whether WP Bannerize version is within 2.0.0 through 4.0.2.
- Identify which authenticated roles can access WP Bannerize administrative functions.
- Review web and WordPress logs for unusual authenticated plugin activity.
- Check whether sensitive data may have been exposed from affected databases.
- Document remediation status for each WordPress site.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-39351 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N3.14Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.7HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/vulnerability-advisories/#CVE-2021-39351CVE reference · x_refsource_MISC
- https://plugins.trac.wordpress.org/browser/wp-bannerize/trunk/Classes/wpBannerizeAdmin.php#L1681CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.