LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25386: WordPress Ally plugin <= 4.0.2 - Broken Access Control vulnerability

Missing Authorization vulnerability in Elementor Ally pojo-accessibility allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Ally: from n/a through <= 4.0.2.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25386 is a broken access control issue in the WordPress Ally plugin by Elementor, affecting versions up to 4.0.2. An unauthenticated network attacker could cause limited integrity impact. This is not listed in CISA KEV, and the provided sources do not show active exploitation.

Executive priority

Treat as a medium-priority WordPress plugin issue. It can be remotely reachable without login, but the documented impact is limited to integrity and there is no cited active exploitation. Prioritize internet-facing WordPress sites and update or remove affected plugin installations once vendor guidance is confirmed.

Technical view

The vulnerability is CWE-862 Missing Authorization in package pojo-accessibility. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact. Public details do not identify the specific vulnerable function or fixed version.

Likely exposure

Exposure is likely limited to WordPress sites running the Ally / pojo-accessibility plugin at version 4.0.2 or earlier. Sites without this plugin are not affected based on the provided sources.

Exploitation context

The CVSS vector indicates unauthenticated remote reachability with low attack complexity. However, the sources do not provide exploit details, proof-of-concept status, or evidence of active exploitation. KEV status is false.

Researcher notes

Public information is sparse. The record identifies missing authorization in Ally / pojo-accessibility through 4.0.2, but does not disclose the endpoint, action, fixed release, or exploit maturity. Avoid assuming broader impact beyond low integrity based on the CVSS vector.

Mitigation direction

  • Inventory WordPress sites for the Ally / pojo-accessibility plugin.
  • Identify any installations running version 4.0.2 or earlier.
  • Check Elementor, WordPress.org, and Patchstack guidance for a fixed version.
  • Update the plugin if a vendor-approved fixed version is available.
  • Disable or remove the plugin where it is not business-critical.

Validation and detection

  • Confirm plugin presence and version in WordPress administrative inventory.
  • Compare installed versions against the affected range: through 4.0.2.
  • Review vendor advisories for updated remediation details.
  • Check site logs for unexpected unauthenticated changes or plugin-related activity.
  • Document affected sites, remediation status, and compensating controls.
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-25386 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
ElementorAllypojo-accessibility, 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.