Skip to content

Multiple Authorization Vulnerabilities in Title Generation Ability

Low
jeffpaul published GHSA-mxf5-gp98-93wv Jan 27, 2026

Package

composer wordpress/ai (Composer)

Affected versions

< 0.2.1

Patched versions

0.2.1

Description

Impact

Successful exploitation of these vulnerabilities may allow a low-privileged authenticated attacker to access or infer information from password-protected content and to consume AI generation resources beyond intended limits.

The potential impacts include:

  • Unauthorized disclosure of sensitive or confidential information
  • Excessive consumption of AI API resources resulting in financial cost to the site owner
  • Degradation or denial of AI-powered functionality due to exhausted API quotas
  • Reduced availability of AI features for legitimate users

Attack complexity is low and does not require elevated privileges beyond an authenticated account. No user interaction from a privileged user is required.

Patch

The issues were fixed in AI Experiments version 0.2.1, released on 26 January 2026. No further action is required after updating.

Workarounds

If immediate updating is not possible, consider these interim mitigations:

  • Disable Title Generation for Subscriber roles
  • Restrict AI features to Author role and above
  • Monitor AI API usage for anomalies

Note: These are temporary mitigations only and do not fully address the vulnerabilities.

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N

CVE ID

No known CVE

Weaknesses

No CWEs

Credits