CVE-2024-4858: WP Testimonial Carousel: OpenAI API key hijack, no auth
MEDIUM PoC AVAILABLEAny unauthenticated attacker can overwrite the OpenAI API key in Testimonial Carousel for Elementor (≤10.2.0), disabling AI features or substituting attacker-controlled credentials. Update to 10.2.1+ immediately and rotate your OpenAI API key — assume it may have been tampered with. If patching is delayed, deactivate the plugin.
Risk Assessment
Medium CVSS but trivial to exploit at scale. Zero authentication required, network-accessible, low complexity — ideal for automated WordPress scanner campaigns. Impact is confined to integrity of AI configuration rather than data exfiltration or code execution, but the zero-barrier exploitation lowers the effective risk threshold for opportunistic attackers mass-scanning WordPress deployments.
Affected Systems
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| testimonial_carousel_for_elementor | — | — | No patch |
Do you use testimonial_carousel_for_elementor? You're affected.
Severity & Risk
Attack Surface
Recommended Action
6 steps-
Patch: update to version 10.2.1 or later.
-
Rotate your OpenAI API key immediately post-patch — treat the stored key as compromised.
-
If patching is delayed, deactivate the plugin entirely.
-
Add OpenAI API usage alerts to detect anomalous spend or unexpected key changes.
-
Review server logs for unauthenticated POST requests to wp-admin/admin-ajax.php targeting action=save_testimonials_option_callback.
-
Audit all WordPress plugins storing third-party AI API keys for similar missing-capability-check patterns.
CISA SSVC Assessment
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
Classification
Compliance Impact
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2024-4858?
Any unauthenticated attacker can overwrite the OpenAI API key in Testimonial Carousel for Elementor (≤10.2.0), disabling AI features or substituting attacker-controlled credentials. Update to 10.2.1+ immediately and rotate your OpenAI API key — assume it may have been tampered with. If patching is delayed, deactivate the plugin.
Is CVE-2024-4858 actively exploited?
Proof-of-concept exploit code is publicly available for CVE-2024-4858, increasing the risk of exploitation.
How to fix CVE-2024-4858?
1. Patch: update to version 10.2.1 or later. 2. Rotate your OpenAI API key immediately post-patch — treat the stored key as compromised. 3. If patching is delayed, deactivate the plugin entirely. 4. Add OpenAI API usage alerts to detect anomalous spend or unexpected key changes. 5. Review server logs for unauthenticated POST requests to wp-admin/admin-ajax.php targeting action=save_testimonials_option_callback. 6. Audit all WordPress plugins storing third-party AI API keys for similar missing-capability-check patterns.
What systems are affected by CVE-2024-4858?
This vulnerability affects the following AI/ML architecture patterns: WordPress AI plugin integrations, OpenAI API integrations, AI-powered content generation pipelines.
What is the CVSS score for CVE-2024-4858?
CVE-2024-4858 has a CVSS v3.1 base score of 5.3 (MEDIUM). The EPSS exploitation probability is 0.19%.
Technical Details
NVD Description
The Testimonial Carousel For Elementor plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'save_testimonials_option_callback' function in versions up to, and including, 10.2.0. This makes it possible for unauthenticated attackers to update the OpenAI API key, disabling the feature.
Exploitation Scenario
Attacker enumerates WordPress sites running Testimonial Carousel for Elementor via plugin version fingerprinting (readme.txt, response headers). Without any credentials, sends a crafted POST to /wp-admin/admin-ajax.php with action=save_testimonials_option_callback and a malicious openai_api_key parameter. Plugin stores the value without authorization check. AI testimonial generation immediately fails (DoS) or routes through attacker's OpenAI account. Full attack chain is automatable — a single scan-and-exploit script can compromise thousands of sites simultaneously.
Weaknesses (CWE)
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N References
- plugins.trac.wordpress.org/browser/testimonials-carousel-elementor/trunk/class-testimonials-carousel-elementor.php Product
- plugins.trac.wordpress.org/changeset/3092154/testimonials-carousel-elementor/trunk/class-testimonials-carousel-elementor.php Patch
- wordfence.com/threat-intel/vulnerabilities/id/1f589345-a081-4d27-ac4a-6edc44b96f91 3rd Party
- github.com/fkie-cad/nvd-json-data-feeds Exploit
Timeline
Related Vulnerabilities
CVE-2026-21858 10.0 n8n: Input Validation flaw enables exploitation
Same attack type: Auth Bypass GHSA-vvpj-8cmc-gx39 10.0 picklescan: security flaw enables exploitation
Same attack type: Auth Bypass CVE-2025-2828 10.0 LangChain RequestsToolkit: SSRF exposes cloud metadata
Same attack type: Auth Bypass CVE-2025-53767 10.0 Azure OpenAI: SSRF EoP, no auth required (CVSS 10)
Same attack type: Auth Bypass CVE-2026-26030 10.0 semantic-kernel: Code Injection enables RCE
Same attack type: Auth Bypass
AI Threat Alert