dbcve.org
Peprodev Ultimate InvoiceWordPress extension · Peprodev

CVE-2024-25933

HIGH · 7.5 CVSS v3.1 Published 2024-03-17
Fix available
A fix is available. Upgrade to 1.9.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Pepro Dev. Group PeproDev Ultimate Invoice.This issue affects PeproDev Ultimate Invoice: from n/a through 1.9.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The vulnerability allows unauthorized actors to access sensitive information in PeproDev Ultimate Invoice plugin versions up to 1.9.7. The exact attack vector and specific data exposed are not detailed in available references, but the CVSS 7.5 score indicates significant sensitive data exposure without authentication or with minimal privileges.

MitigationUpdate PeproDev Ultimate Invoice to the latest version beyond 1.9.7, which should contain the patched access controls. If no update is available, restrict access to the plugin's endpoints via web server configuration or disable the plugin until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Peprodev Ultimate InvoiceWordPress extension
Affected:< 1.9.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate PeproDev Ultimate Invoice plugin
    In WordPress admin panel, go to Plugins > Installed Plugins and search for 'Ultimate Invoice' or 'PeproDev'. Note the listed version number.
    Affected if The plugin is installed and the version shown is 1.9.7 or lower (< 1.9.8)
  2. Verify plugin version via filesystem
    If you have file system access, check the plugin main file (usually wp-content/plugins/ultimate-invoice/ultimate-invoice.php or similar) for the 'Version' header in the plugin comments.
    Affected if The Version header reads 1.9.7 or lower
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, check if Ultimate Invoice shows as 'Active' (not just installed).
    Affected if The plugin is activated and version is below 1.9.8
  4. Review access to plugin endpoints
    Attempt to access common plugin-related URLs on your site such as /?p=...&action=ui_view_invoice or similar invoice viewing endpoints, checking if sensitive invoice data is returned without authentication.
    Affected if Invoice data or sensitive information is returned without login credentials

Your environment is affected if PeproDev Ultimate Invoice plugin version 1.9.7 or lower is installed and active on your WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.8 or later
Fixed in 1.9.8
Interim mitigation

Update PeproDev Ultimate Invoice to the latest version beyond 1.9.7, which should contain the patched access controls. If no update is available, restrict access to the plugin's endpoints via web server configuration or disable the plugin until a patch is released.

Recommended fix Moderate confidence

Upgrade to PeproDev Ultimate Invoice version 1.9.8

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'PeproDev Ultimate Invoice' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.9.8
  5. 5. Alternatively, download version 1.9.8 from a trusted source (such as the official WordPress plugin repository or PeproDev's official website)
  6. 6. Deactivate the existing plugin, delete it, then upload and install the new version
  7. 7. After updating, verify the plugin is functioning correctly and review any settings

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Peprodev Ultimate Invoice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25933 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25933 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data