LiveActive security incident?Get immediate response
CVE Record

CVE-2025-23800: WordPress OrangeBox plugin <= 3.0.0 - CSRF to Stored XSS vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in nova706 OrangeBox orangebox allows Cross Site Request Forgery.This issue affects OrangeBox: from n/a through <= 3.0.0.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects WordPress sites using the OrangeBox plugin through version 3.0.0. A tricked administrator or authorized user could cause malicious content to be stored in the site, creating a persistent browser-side risk for later visitors.

Executive priority

Prioritize remediation on externally accessible WordPress sites, especially those with administrative users who handle email or web links. The issue is high severity, but the available sources do not show confirmed active exploitation.

Technical view

CVE-2025-23800 is a CSRF issue in nova706 OrangeBox that can lead to stored XSS. The published CVSS 3.1 score is 7.1 with network attack vector, low complexity, no privileges required, user interaction required, and changed scope.

Likely exposure

Exposure is likely limited to WordPress installations with the OrangeBox plugin package "orangebox" installed and enabled at version 3.0.0 or earlier. The source bundle does not provide CPEs or a named fixed version.

Exploitation context

The bundle does not state active exploitation, and KEV is false. The CVSS vector indicates user interaction is required. Treat public-facing WordPress sites with this plugin as higher priority because stored XSS can persist beyond the initial request.

Researcher notes

Evidence is limited to the CVE record and Patchstack entry. The source bundle names CSRF leading to stored XSS but does not include request details, affected code paths, exploit proof, or a fixed version.

Mitigation direction

  • Inventory WordPress sites for the OrangeBox plugin and its installed version.
  • Disable or remove OrangeBox where it is not business-critical.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • Update the plugin if an official patched version is available.
  • Limit administrative access and harden WordPress session protections.

Validation and detection

  • Confirm whether OrangeBox is installed and enabled on each WordPress site.
  • Record plugin versions and flag installations at 3.0.0 or earlier.
  • Review stored site content and plugin-controlled output for unexpected scripts.
  • Check logs for unusual administrative actions around plugin configuration.
  • Verify remediation by confirming the plugin is removed, disabled, or updated.
Prepared
Confidence
medium
Sources
3

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-2025-23800 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-23800Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
nova706OrangeBoxorangebox, 0unaffected
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.