dbcve.org
Peprodev Ultimate InvoiceWordPress extension · Pepro

CVE-2024-13719

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-19
Fix available
A fix is available. Upgrade to after 2.0.8 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The PeproDev Ultimate Invoice plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.0.9 via the invoicing viewer due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to view invoices for completed orders which can contain PII of users.

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 · high confidence

The PeproDev Ultimate Invoice WordPress plugin (versions up to 2.0.9) contains an Insecure Direct Object Reference (IDOR) vulnerability in its invoice viewer. The plugin fails to validate a user-controlled parameter (likely an order/invoice ID), allowing unauthenticated attackers to access arbitrary invoice documents containing PII such as customer names, addresses, and purchase details.

MitigationUpdate the PeproDev Ultimate Invoice plugin to version 2.0.10 or later which includes proper authorization checks on invoice access requests.

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:<= 2.0.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Confirm plugin installation
    Check if the PeproDev Ultimate Invoice plugin is installed on your WordPress site by reviewing the plugin list in the WordPress admin dashboard or inspecting the wp-content/plugins directory
    Affected if Plugin is installed and version is unknown or <= 2.0.8
  2. Identify installed plugin version
    Locate the installed version number from the plugin header in the main plugin file, typically found in the plugin directory under wp-content/plugins/pepultimate-invoice or similar, or check the WordPress plugin repository for the installed version
    Affected if Installed version is <= 2.0.8 (the affected range)
  3. Locate the invoice viewer functionality
    Identify the URL endpoint used for viewing invoices by reviewing plugin documentation, source code, or common WordPress invoice routes (typically contains terms like invoice, view, or download in the URL)
    Affected if Invoice viewer endpoint is accessible to unauthenticated users
  4. Test for IDOR vulnerability
    Attempt to access the invoice viewer endpoint with different invoice ID values while logged out or as a different user to verify if the plugin validates ownership before returning invoice documents
    Affected if Unauthenticated or unauthorized users can access invoices belonging to other customers without proper authorization checks

Your environment is affected if PeproDev Ultimate Invoice plugin version <= 2.0.8 is installed AND the invoice viewer allows unauthenticated access to arbitrary invoice documents containing PII.

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 a release after 2.0.8
Interim mitigation

Update the PeproDev Ultimate Invoice plugin to version 2.0.10 or later which includes proper authorization checks on invoice access requests.

Recommended fix Moderate confidence

2.1.0 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate PeproDev Ultimate Invoice
  4. Check if an update is available and update to version 2.1.0 or higher
  5. If no update is shown in WordPress, manually download the latest version from wordpress.org and reinstall

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13719 — 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-13719 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