LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25410: WordPress WP-CORS plugin <= 0.2.2 - Broken Access Control vulnerability

Missing Authorization vulnerability in tstephenson WP-CORS wp-cors allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP-CORS: from n/a through <= 0.2.2.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25410 affects the WordPress WP-CORS plugin through version 0.2.2. It is a broken access control issue where authorization checks are missing. The published impact is limited: an authenticated low-privilege user could cause low integrity impact. There is no cited evidence of active exploitation.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. Prioritize internet-facing sites with many contributors or subscribers, but this is not currently supported as an emergency exploitation event by the provided sources.

Technical view

The CVE describes CWE-862 Missing Authorization in tstephenson WP-CORS wp-cors <=0.2.2. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, integrity low only. Available sources do not provide exploit details or name a fixed version.

Likely exposure

Exposure is limited to WordPress sites with the WP-CORS plugin installed at version 0.2.2 or earlier. Risk is more relevant where untrusted or numerous low-privilege WordPress accounts exist.

Exploitation context

The vulnerability requires an authenticated low-privilege user and could affect site integrity. It is not listed in CISA KEV in the provided data, and no provided source states active exploitation.

Researcher notes

Public details are sparse. The CVE and Patchstack entry identify broken access control/missing authorization, but do not disclose affected functionality, proof of concept, active exploitation, or a fixed version in the provided bundle.

Mitigation direction

  • Inventory WordPress sites for the WP-CORS plugin and installed version.
  • Check vendor, WordPress plugin, and Patchstack guidance for an updated or remediated version.
  • If no fix is available, consider disabling or removing the plugin where business impact allows.
  • Limit unnecessary low-privilege WordPress accounts until remediation is confirmed.

Validation and detection

  • Confirm whether WP-CORS is installed on each WordPress instance.
  • Record plugin versions and flag 0.2.2 or earlier for review.
  • Review WordPress user roles for unnecessary low-privilege accounts.
  • Monitor vendor and Patchstack entries for remediation updates.
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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2026-25410 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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
2Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-25410Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
tstephensonWP-CORSwp-cors, 0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.