LiveActive security incident?Get immediate response
CVE Record

CVE-2013-10029: Exit Box Lite Plugin wordpress-exit-box-lite.php exitboxadmin cross-site request forgery

A vulnerability classified as problematic was found in Exit Box Lite Plugin up to 1.06 on WordPress. Affected by this vulnerability is the function exitboxadmin of the file wordpress-exit-box-lite.php. The manipulation leads to cross-site request forgery. The attack can be launched remotely. Upgrading to version 1.10 is able to address this issue. The patch is named fad26701addb862c51baf85c6e3cc136aa79c309. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-230671.

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2013-10029 is a cross-site request forgery issue in the WordPress Exit Box Lite plugin, reported for versions up to 1.06. It could let a remote attacker cause unintended plugin-side changes if a legitimate privileged user is tricked into sending a request. Sources name version 1.10 as the fix.

Executive priority

Prioritize remediation during normal vulnerability maintenance unless the plugin is internet-facing on a high-value WordPress site or admin activity appears suspicious. The available evidence supports moderate urgency, mainly because the fix is known and the affected software is old.

Technical view

The issue is CWE-352 in the exitboxadmin function of wordpress-exit-box-lite.php. CVSS v2 is 5.0 with network attack vector, low complexity, no attacker authentication, partial integrity impact, and no confidentiality or availability impact. The cited fix is commit fad26701addb862c51baf85c6e3cc136aa79c309, released as version 1.10.

Likely exposure

Exposure is limited to WordPress sites running Exit Box Lite plugin versions up to 1.06. Because the affected function is an admin function, impact likely depends on a logged-in user with plugin management access, but exact permission details are not fully described in the bundle.

Exploitation context

The sources describe remote CSRF but do not report public exploitation or inclusion in CISA KEV. Treat this as a configuration integrity risk for legacy WordPress installations, not as evidence of active compromise.

Researcher notes

The bundle provides a clear vulnerable component, function name, CWE, CVSS v2 vector, and patch reference. It does not provide detailed request mechanics, exact authorization behavior, or confirmed exploitation. Avoid assuming broader WordPress compromise from this CVE alone.

Mitigation direction

  • Upgrade Exit Box Lite to version 1.10 or later.
  • Remove the plugin if it is no longer required.
  • Check vendor or repository guidance for any additional hardening notes.
  • Review WordPress admin accounts for least-privilege access.

Validation and detection

  • Inventory WordPress sites for the Exit Box Lite plugin.
  • Confirm installed plugin versions are newer than 1.06.
  • Verify the patch commit or version 1.10 is present where applicable.
  • Review administrative change logs for unexpected plugin configuration changes.
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-2013-10029 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-2013-10029Access 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
n/aExit Box Lite Plugin1.06Listed
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.