Loading vulnerability…
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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a working proof-of-concept exploit (CVE-2025-13380.py) for a critical arbitrary file read vulnerability in the 'AI Engine for WordPress: ChatGPT, GPT Content Generator' plugin (versions <= 1.0.1). The exploit requires valid WordPress credentials for a user with at least Contributor privileges. It automates the process of logging in, creating a draft post, and abusing the vulnerable 'lqdai_update_post' AJAX action to supply a 'file://' URL pointing to a sensitive file (such as wp-config.php). The plugin reads the file and writes its contents to the public uploads directory, from which the exploit retrieves and displays the file contents. The repository consists of the main exploit script (CVE-2025-13380.py) and a detailed README.md explaining the vulnerability, exploitation steps, and technical details of the underlying plugin flaw. The exploit demonstrates a real-world attack path and provides clear, actionable intelligence for defenders and testers.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.