CVE-2024-13698: Jobify WP: missing authz allows OpenAI key abuse, SSRF
MEDIUMAny WordPress site running Jobify theme ≤4.2.7 with AI image generation enabled exposes its OpenAI API key to unauthenticated abuse — attackers can drain your API quota and perform SSRF against internal networks. Update to ≥4.2.8 immediately and rotate the OpenAI API key. If patching is not immediate, disable the AI image generation feature or block the vulnerable endpoints at the WAF.
Risk Assessment
Rated Medium (CVSS 6.5) but operationally higher due to zero-barrier exploitation: no auth, no user interaction, network-reachable. The financial exposure from uncapped OpenAI API consumption can far exceed what CVSS captures. SSRF component adds reconnaissance potential against internal infrastructure. Automated scanners will find this quickly given the WordPress ecosystem scale.
Affected Systems
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| jobify | — | — | No patch |
Do you use jobify? You're affected.
Severity & Risk
Attack Surface
Recommended Action
6 steps-
PATCH
Update Jobify theme to version 4.2.8 or later immediately.
-
ROTATE CREDENTIALS
Invalidate and regenerate the OpenAI API key configured in the theme — treat it as compromised.
-
SCOPE THE KEY
Issue a new OpenAI API key scoped only to image generation, with spending limits and rate limits set in the OpenAI dashboard.
-
WAF RULE
Block unauthenticated POST requests to wp-admin/admin-ajax.php with action=download_image_via_ai or action=generate_image_via_ai.
-
AUDIT USAGE
Review OpenAI API usage logs for anomalous generation spikes prior to patching — unexpected costs indicate active exploitation.
-
SSRF MITIGATION
Ensure the web server cannot reach internal/cloud metadata endpoints (169.254.169.254, 100.64.0.0/10) via egress filtering.
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-13698?
Any WordPress site running Jobify theme ≤4.2.7 with AI image generation enabled exposes its OpenAI API key to unauthenticated abuse — attackers can drain your API quota and perform SSRF against internal networks. Update to ≥4.2.8 immediately and rotate the OpenAI API key. If patching is not immediate, disable the AI image generation feature or block the vulnerable endpoints at the WAF.
Is CVE-2024-13698 actively exploited?
No confirmed active exploitation of CVE-2024-13698 has been reported, but organizations should still patch proactively.
How to fix CVE-2024-13698?
1. PATCH: Update Jobify theme to version 4.2.8 or later immediately. 2. ROTATE CREDENTIALS: Invalidate and regenerate the OpenAI API key configured in the theme — treat it as compromised. 3. SCOPE THE KEY: Issue a new OpenAI API key scoped only to image generation, with spending limits and rate limits set in the OpenAI dashboard. 4. WAF RULE: Block unauthenticated POST requests to wp-admin/admin-ajax.php with action=download_image_via_ai or action=generate_image_via_ai. 5. AUDIT USAGE: Review OpenAI API usage logs for anomalous generation spikes prior to patching — unexpected costs indicate active exploitation. 6. SSRF MITIGATION: Ensure the web server cannot reach internal/cloud metadata endpoints (169.254.169.254, 100.64.0.0/10) via egress filtering.
What systems are affected by CVE-2024-13698?
This vulnerability affects the following AI/ML architecture patterns: AI-enabled web applications (WordPress + OpenAI integration), Shared API key architectures, Cloud-hosted web servers with SSRF exposure to metadata endpoints.
What is the CVSS score for CVE-2024-13698?
CVE-2024-13698 has a CVSS v3.1 base score of 6.5 (MEDIUM). The EPSS exploitation probability is 0.47%.
Technical Details
NVD Description
The Jobify - Job Board WordPress Theme for WordPress is vulnerable to unauthorized access and modification of data due to a missing capability check on the 'download_image_via_ai' and 'generate_image_via_ai' functions in all versions up to, and including, 4.2.7. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application to upload files in an image format, and to generate AI images using the site's OpenAI key.
Exploitation Scenario
An unauthenticated attacker scans for WordPress sites running Jobify using WPScan or passive techniques. They issue a POST to /wp-admin/admin-ajax.php with action=generate_image_via_ai — no credentials required. The server uses the site's OpenAI API key to generate arbitrary images, billed to the victim. In parallel, the attacker abuses download_image_via_ai to trigger outbound HTTP requests to internal addresses (e.g., AWS metadata endpoint http://169.254.169.254/latest/meta-data/) to harvest cloud credentials. Both attack paths are trivially automatable and can be executed against thousands of Jobify installations in bulk.
Weaknesses (CWE)
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N References
Timeline
Related Vulnerabilities
CVE-2026-21858 10.0 n8n: Input Validation flaw enables exploitation
Same attack type: Data Extraction CVE-2025-53767 10.0 Azure OpenAI: SSRF EoP, no auth required (CVSS 10)
Same attack type: Data Extraction CVE-2023-3765 10.0 MLflow: path traversal allows arbitrary file read
Same attack type: Data Extraction CVE-2025-2828 10.0 LangChain RequestsToolkit: SSRF exposes cloud metadata
Same attack type: Data Extraction GHSA-vvpj-8cmc-gx39 10.0 picklescan: security flaw enables exploitation
Same attack type: Auth Bypass
AI Threat Alert