LiveActive security incident?Get immediate response
CVE Record

CVE-2012-10015: BestWebSoft Twitter Plugin Settings Page twitter.php twttr_settings_page cross-site request forgery

A vulnerability was found in BestWebSoft Twitter Plugin up to 2.14 on WordPress. It has been classified as problematic. Affected is the function twttr_settings_page of the file twitter.php of the component Settings Page. The manipulation leads to cross-site request forgery. It is possible to launch the attack remotely. Upgrading to version 2.15 is able to address this issue. The patch is identified as a6d4659cbb2cbf18ccb0fb43549d5113d74e0146. It is recommended to upgrade the affected component. VDB-230154 is the identifier assigned to this vulnerability.

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2012-10015 is a cross-site request forgery issue in the BestWebSoft Twitter Plugin for WordPress, versions 2.0 through 2.14. An attacker could remotely cause unintended changes through the plugin settings page. The cited sources name version 2.15 as the fixed release.

Executive priority

Address during normal vulnerability remediation unless the plugin is broadly deployed on high-value WordPress sites. The business risk is unauthorized settings changes, not confirmed compromise or outage from the provided sources.

Technical view

The flaw affects twttr_settings_page in twitter.php for the Settings Page component. It is classified as CWE-352 CSRF with CVSS 2.0 score 5.0: network reachable, low complexity, no authentication, partial integrity impact, and no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites running BestWebSoft Twitter Plugin versions 2.0 through 2.14. Sites not using this plugin, or already upgraded to version 2.15 or later, are not identified as affected by the provided sources.

Exploitation context

The source bundle says remote exploitation is possible, but does not cite active exploitation. The CVE is not marked as CISA KEV. Treat this as a settings-integrity risk rather than a direct data theft or service outage issue based on the available evidence.

Researcher notes

The evidence identifies affected versions, component, function, CWE, CVSS vector, and a fixing commit. The bundle does not describe exact request mechanics, prerequisites involving user interaction, or observed exploitation, so validation should focus on version inventory and patch confirmation.

Mitigation direction

  • Upgrade BestWebSoft Twitter Plugin to version 2.15 or later.
  • Prioritize internet-facing WordPress sites where administrators actively use the plugin.
  • Review plugin settings for unexpected changes after remediation.
  • Check vendor guidance if using a forked or archived plugin copy.

Validation and detection

  • Inventory WordPress sites for BestWebSoft Twitter Plugin versions 2.0 through 2.14.
  • Confirm affected installations have been upgraded to version 2.15 or later.
  • Review WordPress admin activity for suspicious plugin settings changes.
  • Verify the deployed plugin code includes the referenced patch commit.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2012-10015 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:N/C:N/I:P/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5CVSS 2.0MediumAV:N/AC:L/Au:N/C:N/I:P/A:N102.9Primary CVE score

Vulnerability scoring details

Base CVSS 2.0 score

5Medium
CVSS 2.0 vector shape for CVE-2012-10015Access VectorAccess ComplexityAuthenticationConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: AV:N/AC:L/Au:N/C:N/I:P/A:N

Access Vector
NetworkAdjacentLocal
Access Complexity
LowMediumHigh
Authentication
NoneSingleMultiple
Confidentiality Impact
CompletePartialNone
Integrity Impact
CompletePartialNone
Availability Impact
CompletePartialNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
BestWebSoftTwitter Plugin2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.