LiveActive security incident?Get immediate response
CVE Record

CVE-2012-10017: BestWebSoft Portfolio Plugin cross-site request forgery

A vulnerability was found in BestWebSoft Portfolio Plugin up to 2.04 on WordPress. It has been classified as problematic. This affects an unknown part. The manipulation leads to cross-site request forgery. It is possible to initiate the attack remotely. Upgrading to version 2.06 is able to address this issue. The patch is named 68af950330c3202a706f0ae9bbb52ceaa17dda9d. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-248955.

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-risk CSRF issue in the BestWebSoft Portfolio Plugin for WordPress. A remote attacker could potentially cause an affected site to perform unintended portfolio-related actions if the right user interaction and permissions exist. The source says upgrading to version 2.06 addresses it.

Executive priority

Prioritize remediation during normal vulnerability management cycles, faster for externally managed or business-critical WordPress sites. The issue affects integrity, not confidentiality or availability, and the provided sources do not show active exploitation.

Technical view

CVE-2012-10017 is CWE-352 affecting BestWebSoft Portfolio Plugin up to 2.04. The CVSS 2.0 vector is AV:N/AC:L/Au:N/C:N/I:P/A:N, indicating network reachability, low complexity, and partial integrity impact only. The exact vulnerable component is not identified in the bundle.

Likely exposure

Exposure is likely limited to WordPress sites running BestWebSoft Portfolio Plugin version 2.04 or earlier. The bundle provides no CPEs and does not identify hosted-service exposure. Asset teams should verify plugin inventories directly across WordPress estates.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, or a public exploit. It states remote initiation is possible, but does not provide the affected action, required user role, or practical exploitation conditions. Treat exploitation evidence as incomplete.

Researcher notes

The record is sparse: it identifies CSRF, affected versions up to 2.04, CVSS 5.0, and a patch commit. It does not name the vulnerable endpoint, nonce failure, user role, or affected workflow. Avoid assuming exploitability details beyond the cited records.

Mitigation direction

  • Upgrade BestWebSoft Portfolio Plugin to version 2.06 or later.
  • Remove or disable the plugin where it is no longer required.
  • Limit WordPress administrative access until affected sites are updated.
  • Monitor CVE, vendor, and VulDB records for any additional guidance.

Validation and detection

  • Inventory WordPress sites for the BestWebSoft Portfolio Plugin.
  • Confirm installed plugin versions are 2.06 or later.
  • Check whether any sites still run version 2.04 or earlier.
  • Review WordPress change history for unexpected portfolio-related modifications.
Prepared
Confidence
medium
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-10017 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-10017Access 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
BestWebSoftPortfolio Plugin2.04Listed
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.