Security readout for executives and security teams
Plain-English summary
CVE-2012-10012 affects the BestWebSoft Facebook Like Button WordPress plugin through version 2.13. It is a cross-site request forgery issue that could let an attacker cause settings changes if they can trick a site administrator into acting while authenticated.
Executive priority
Treat as a targeted website integrity risk, not an emergency breach signal. Prioritize remediation for externally administered WordPress sites, high-traffic properties, and sites where plugin settings could affect brand trust or user interaction.
Technical view
The reported flaw is CWE-352 in fcbk_bttn_plgn_settings_page within facebook-button-plugin.php. The CVSS 2.0 vector is AV:N/AC:L/Au:N/C:N/I:P/A:N, indicating remote low-complexity integrity impact without confidentiality or availability impact. A patch commit is identified by the sources.
Likely exposure
Exposure is limited to WordPress sites running BestWebSoft Facebook Like Button versions 2.0 through 2.13. Business risk is mainly unauthorized plugin configuration changes, not direct data theft or service outage based on the provided CVSS impact.
Exploitation context
The source bundle describes remote exploitability, but does not provide evidence of active exploitation. CISA KEV status is false. Because this is CSRF, practical abuse likely depends on interaction from an authenticated administrator or similarly privileged user.
Researcher notes
Evidence identifies the vulnerable function, file, affected version range, CWE, CVSS vector, and patch commit. The sources do not establish public exploitation, exploit maturity, or downstream impact beyond partial integrity compromise.
Mitigation direction
- Inventory WordPress sites for the affected plugin and versions.
- Upgrade beyond affected versions or apply the referenced vendor patch.
- Remove the plugin where it is unused or unmaintained.
- Review plugin settings for unauthorized or unexpected changes.
- Check current vendor guidance before relying on any workaround.
Validation and detection
- Confirm installed plugin versions are not 2.0 through 2.13.
- Verify the referenced patch commit is present where source is managed.
- Review WordPress admin activity for unexpected plugin setting changes.
- Confirm plugin settings pages include appropriate CSRF protection after remediation.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2012-10012 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
- Medium
- CVSS
- 5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:N/I:P/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.
AV:N/AC:L/Au:N/C:N/I:P/A:N102.9Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
5MediumVector: AV:N/AC:L/Au:N/C:N/I:P/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://vuldb.com/?id.225355CVE reference · vdb-entry, technical-description
- https://vuldb.com/?ctiid.225355CVE reference · signature, permissions-required
- https://github.com/wp-plugins/facebook-button-plugin/commit/33144ae5a45ed07efe7fceca901d91365fdbf7cbCVE reference · patch
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.