CVE-2025-13380 json
AI Engine for WordPress: ChatGPT, GPT Content Generator <= 1.0.1 - Authenticated (Contributor+) Arbitrary File Read
published 2025-11-25 11 mo ago modified 2026-10-18 21 d ago also EUVD-2025-199570
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
The AI Engine for WordPress: ChatGPT, GPT Content Generator plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 1.0.1. This is due to insufficient validation of user-supplied file paths in the 'lqdai_update_post' AJAX endpoint and the use of file_get_contents() with user-controlled URLs without protocol restrictions in the insert_image() function. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11 mo ago
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- liquidthemes AI Engine for WordPress: ChatGPT, GPT Content Generator
Classification
- Weakness
-
- CWE-73 External Control of File Name or Path
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/ae0abace-9bf6-4ef9-a9b8-7efffbf25628?source=cve
- plugins.trac.wordpress.org /browser/liquid-chatgpt/tags/1.0.1/liquid-chatgpt.php#L83
- plugins.trac.wordpress.org /browser/liquid-chatgpt/tags/1.0.1/liquid-chatgpt.php#L315
- plugins.trac.wordpress.org /browser/liquid-chatgpt/tags/1.0.1/liquid-chatgpt.php#L423
- github.com /d0n601/CVE-2025-13380
- ryankozak.com /posts/cve-2025-13380/
Sources
- CVE List CVE-2025-13380
- NVD CVE-2025-13380
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.