CVE-2024-11896: Stored XSS — MEDIUM

CISO Take

A WordPress plugin integrating ChatGPT/OpenAI exposes stored XSS exploitable by any contributor-level user — primary risk is OpenAI API key theft and admin session hijacking. Patch immediately to a version above 1.0.7 or disable the plugin entirely. Rotate any OpenAI API keys configured in the plugin and audit all contributor accounts on AI-enabled WordPress sites.

What is the risk?

Medium severity in isolation, but elevated in AI-integrated environments. Low attack complexity post-authentication makes this trivially exploitable by anyone with contributor access — a low bar in editorial CMS environments. The main AI-specific risk multiplier is the likely presence of OpenAI API keys in the plugin configuration, which if exfiltrated enable unauthorized inference at the victim's cost and expose data sent to the API.

How severe is it?

CVSS 3.1

6.4 / 10

EPSS

0.3%

chance of exploitation in 30 days

Higher than 24% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

Exploit Available

Exploitation: MEDIUM

Sophistication

Trivial

Exploitation Confidence

medium

○ Public PoC indexed (trickest/cve)

Composite signal derived from CISA KEV, VulnCheck KEV, CISA SSVC, EPSS, Metasploit, Exploit-DB, trickest/cve, Nuclei templates, and inthewild.io exploitation reports.

What is the attack surface?

AV Network

AC Low

PR Low

UI None

S Changed

C Low

I Low

A None

What should I do?

7 steps

Update Text Prompter plugin to a version above 1.0.7 immediately via WordPress dashboard.
If no patch is available, disable the plugin and purge all text_prompter shortcodes from existing content.
Rotate all OpenAI API keys configured in this plugin — treat them as compromised.
Audit contributor-level WordPress accounts; restrict to minimum necessary trusted users.
Scan pages and posts for unexpected script tags or obfuscated JavaScript injected via shortcodes.
Enable WAF rules targeting WordPress shortcode attribute injection patterns.
Review OpenAI API usage logs for anomalous activity over the past 90 days.

What does CISA's SSVC say?

Decision Track

Exploitation none

Automatable No

Technical Impact partial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Code Execution Data Extraction Plugin API AML.T0034 - Cost Harvesting AML.T0040 - AI Model Inference API Access AML.T0049 - Exploit Public-Facing Application AML.T0055 - Unsecured Credentials

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001

A.6.2.5 - AI System Security and Privacy Controls

NIST AI RMF

MANAGE-2.2 - Treatment of Identified AI Risks

OWASP LLM Top 10

LLM02 - Insecure Output Handling LLM07 - Insecure Plugin Design

Frequently Asked Questions

What is CVE-2024-11896?

A WordPress plugin integrating ChatGPT/OpenAI exposes stored XSS exploitable by any contributor-level user — primary risk is OpenAI API key theft and admin session hijacking. Patch immediately to a version above 1.0.7 or disable the plugin entirely. Rotate any OpenAI API keys configured in the plugin and audit all contributor accounts on AI-enabled WordPress sites.

Is CVE-2024-11896 actively exploited?

Proof-of-concept exploit code is publicly available for CVE-2024-11896, increasing the risk of exploitation.

How to fix CVE-2024-11896?

1. Update Text Prompter plugin to a version above 1.0.7 immediately via WordPress dashboard. 2. If no patch is available, disable the plugin and purge all text_prompter shortcodes from existing content. 3. Rotate all OpenAI API keys configured in this plugin — treat them as compromised. 4. Audit contributor-level WordPress accounts; restrict to minimum necessary trusted users. 5. Scan pages and posts for unexpected script tags or obfuscated JavaScript injected via shortcodes. 6. Enable WAF rules targeting WordPress shortcode attribute injection patterns. 7. Review OpenAI API usage logs for anomalous activity over the past 90 days.

What systems are affected by CVE-2024-11896?

This vulnerability affects the following AI/ML architecture patterns: WordPress AI plugin integrations, LLM API integrations, CMS-based AI content pipelines.

What is the CVSS score for CVE-2024-11896?

CVE-2024-11896 has a CVSS v3.1 base score of 6.4 (MEDIUM). The EPSS exploitation probability is 0.32%.

What is the AI security impact?

Affected AI Architectures

WordPress AI plugin integrationsLLM API integrationsCMS-based AI content pipelines

MITRE ATLAS Techniques

AML.T0034 Cost Harvesting

AML.T0040 AI Model Inference API Access

AML.T0049 Exploit Public-Facing Application

AML.T0055 Unsecured Credentials

Compliance Controls Affected

ISO 42001: A.6.2.5

NIST AI RMF: MANAGE-2.2

OWASP LLM Top 10: LLM02, LLM07

What are the technical details?

Original Advisory

The Text Prompter – Unlimited chatgpt text prompts for openai tasks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'text_prompter' shortcode in all versions up to, and including, 1.0.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Exploitation Scenario

An attacker with contributor access (e.g., via compromised editor credentials or a malicious insider) creates a page embedding a text_prompter shortcode with a malicious onload or event attribute containing JavaScript. The payload is stored server-side. When an administrator previews or visits the page, the script fires in their privileged browser context — exfiltrating session cookies and any API keys visible in the admin interface to an attacker-controlled endpoint. The attacker then uses the stolen OpenAI API key for unauthorized inference, data harvesting, or cost abuse against the victim organization's quota.

Weaknesses (CWE)

CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

CWE-79 — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'): The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

[Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
[Implementation, Architecture and Design] Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies. For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters. Parts of the same output document may require different encodings, which will vary depending on whether the output is in the: etc. Note that HTML Entity Encoding is only appropriate for the HTML body. Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed. HTML body Element attributes (such as src="XYZ") URIs JavaScript sections Casca

Source: MITRE CWE corpus.