Loading vulnerability…
CVE-2025-6082 affects the Birth Chart Compatibility plugin for WordPress in all versions up to and including 2.0. The issue is a full path disclosure caused by insufficient protection against direct access to the plugin's index.php file. When that file is requested directly, the application generates an error message that reveals the full filesystem path of the WordPress installation or plugin directory. This discloses internal path information to unauthenticated users and can assist attackers in reconnaissance and in developing or chaining follow-on attacks against the affected site.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a proof-of-concept (PoC) exploit for CVE-2025-6082, a Full Path Disclosure vulnerability in the 'Birth Chart Compatibility' WordPress plugin (versions 2.0 and below). The repository consists of three files: a LICENSE, a README.md with detailed usage instructions, and the main exploit code in 'exploit.c'. The exploit is written in C and uses libcurl to send HTTP GET requests to the vulnerable plugin's 'index.php' endpoint. It parses the HTTP response for PHP warning or error messages that reveal the server's filesystem path, which can be used for further attacks such as LFI or RCE. The exploit supports options for specifying the target URL, using cookies, enabling verbose output, and repeating requests. The main entry point is 'exploit.c', and the primary fingerprintable endpoint is '/wp-content/plugins/birth-chart-compatibility/index.php'. The exploit is a functional PoC and does not provide a weaponized or post-exploitation payload.
8 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.