LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25391: WordPress WP Wand plugin <= 1.3.07 - Broken Access Control vulnerability

Missing Authorization vulnerability in WP Grids WP Wand ai-content-generation allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Wand: from n/a through <= 1.3.07.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25391 is a broken access control issue in the WordPress WP Wand plugin, package ai-content-generation, affecting versions up to 1.3.07. An authenticated user may perform actions they should not be authorized to perform. The published severity is medium, with limited integrity and availability impact and no stated confidentiality impact.

Executive priority

Treat as a medium-priority WordPress application risk. Prioritize sites that allow user registration, have many low-privileged users, or support business-critical publishing workflows. There is no cited evidence of active exploitation, but broken authorization can enable unauthorized changes or disruption.

Technical view

The issue is CWE-862 Missing Authorization in WP Grids WP Wand ai-content-generation through version 1.3.07. CVSS 3.1 is 5.4: network exploitable, low attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality impact, low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites running WP Wand ai-content-generation plugin version 1.3.07 or earlier. The CVSS vector indicates exploitation requires a low-privileged authenticated account, so public registration or many contributor-level accounts could increase practical risk.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation. Patchstack identifies the vulnerability class and affected range, but no exploit details or abuse evidence are provided in the supplied sources.

Researcher notes

Evidence is limited to CVE metadata and Patchstack’s vulnerability entry. No fix version, proof of concept, or exploitation-in-the-wild claim is included in the supplied sources. Avoid assuming unauthenticated impact; CVSS states privileges required are low.

Mitigation direction

  • Inventory WordPress sites for WP Wand ai-content-generation plugin usage.
  • Identify plugin versions and flag installations at or below 1.3.07.
  • Check Patchstack and vendor guidance for an updated fixed version or workaround.
  • Restrict unnecessary WordPress user accounts, especially low-privileged accounts.
  • Disable the plugin where business impact is acceptable until guidance is confirmed.

Validation and detection

  • Confirm whether the plugin slug ai-content-generation is installed on each WordPress site.
  • Review plugin version information in WordPress administration or asset inventory.
  • Check whether public user registration is enabled on affected sites.
  • Review recent administrative activity for unexpected plugin-related changes.
  • Document remediation status and reassess after vendor or Patchstack updates.
Prepared
Confidence
high
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-25391 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.4 (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: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
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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-25391Attack 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:L

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
WP GridsWP Wandai-content-generation, 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.