PeproDev Ultimate Invoice <= 1.9.7 - Unauthenticated Sensitive Information Exposure via init_plugin
Strategic Overview
- Status
- Patched in 1.9.8
- Affected Plugin
- PeproDev Ultimate Invoice
- Affected Version
<= 1.9.7- CVSS
- 7.5High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-25933
At a glance
CVE-2024-25933 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the PeproDev Ultimate Invoice WordPress plugin, affecting versions <= 1.9.7. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.9.8; sites on affected versions should update now. Disclosed February 2024, reported by Abdi Pranata.
Vulnerability Overview
The PeproDev Ultimate Invoice plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.9.7 via the 'init_plugin' function. This makes it possible for unauthenticated attackers to generate PDF or ZIP files of arbitrary invoices and extract sensitive data.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
PeproDev Ultimate Invoice <= 1.9.7 carries this weakness at init_plugin, and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For PeproDev Ultimate Invoice the fix is 1.9.8: builds <= 1.9.7 are affected, anything from 1.9.8 onward is not.
Remediation
Update to version 1.9.8, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: PeproDev Ultimate Invoice 1.9.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in PeproDev Ultimate Invoice
- 7.2CVE-2026-65510: PeproDev Ultimate Invoice <= 2.2.6 Stored XSS
CVE-2026-65510 - 7.2CVE-2026-65516: PeproDev Ultimate Invoice <= 2.2.6 SSRF
CVE-2026-65516 - 6.4CVE-2024-49298: PeproDev Ultimate Invoice <= 2.0.6 Stored XSS
CVE-2024-49298 - 5.3CVE-2026-65499: PeproDev Ultimate Invoice Missing Authorization
CVE-2026-65499 - 5.3CVE-2024-13719: PeproDev Ultimate Invoice IDOR
CVE-2024-13719 - 5.3CVE-2024-32518: PeproDev Ultimate Invoice Missing Authorization
CVE-2024-32518
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C