Exeebit's vulnerability footprint centers on a narrowly scoped set of WordPress-related plugins, including phpinfo-wp and disable_auto_updates, that handle administrative and information-disclosure functions. The durable signal across its disclosures reflects web-application input and session handling concerns, principally cross-site request forgery and inadvertent exposure of sensitive system information. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Exeebit over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-26542HIGH Cross-Site Request Forgery (CSRF) vulnerability in Exeebit phpinfo() WP plugin <= 4.0 versions. | Nov 22, 2023 | 8.8 | 23 | NO | NO |
CVE-2024-35776HIGH Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Exeebit phpinfo() WP.This issue affects phpinfo() WP: from n/a through 5.0. | Jun 21, 2024 | 7.5 | 22 | NO | NO |
CVE-2024-13336MEDIUM The Disable Auto Updates plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4. This is due to missing or incorrect nonce valid | Feb 19, 2025 | 4.3 | 15 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Exeebit.
Media articles that mention a CVE ID that affects a product developed by Exeebit — matched by CVE ID, not by vendor name.