dbcve.org
Wp ErpWordPress extension · Wedevs

CVE-2024-0913

HIGH · 7.2 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to after 1.12.9 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 WP ERP | Complete HR solution with recruitment & job listings | WooCommerce CRM & Accounting plugin for WordPress is vulnerable to time-based SQL Injection via the erp/v1/accounting/v1/transactions/sales REST API endpoint in all versions up to, and including, 1.13.0 due to insufficient escaping on the user supplied status and customer_id parameters and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with accounting manager or admin privileges and higher to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 WP ERP plugin for WordPress contains a time-based SQL injection vulnerability in the erp/v1/accounting/v1/transactions/sales REST API endpoint. The status and customer_id parameters are not properly escaped, and the SQL query lacks prepared statements, allowing authenticated users with accounting manager or admin privileges to inject arbitrary SQL queries and extract sensitive database information.

MitigationUpdate the WP ERP plugin to version 1.13.1 or later where the vendor has patched the SQL injection vulnerability by implementing proper parameter escaping and prepared statements.

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
Wp ErpWordPress extension
Affected:<= 1.12.9

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 WP ERP plugin is installed
    Check WordPress plugins directory for 'wp-erp' folder, or use 'wp plugin list' command if wp-cli is available
    Affected if WP ERP plugin files exist in the WordPress installation
  2. Identify installed WP ERP version
    View the plugin main file (usually wp-erp.php) header for Version field, or check in WordPress admin under Plugins > Installed Plugins
    Affected if Version is 1.12.9 or lower (any version <= 1.12.9)
  3. Verify plugin is active
    Check WordPress database in wp_options table for option_name 'active_plugins', or check via WordPress admin plugins page
    Affected if WP ERP appears in the list of active plugins
  4. Check for users with accounting manager or admin role
    Query wp_users and wp_usermeta tables for users with 'erp_acconting_manager', 'administrator', or 'erp_manager' roles, or review user roles in WordPress admin under Users
    Affected if Any user account exists with accounting manager or administrator role

The environment is affected if WP ERP version 1.12.9 or lower is installed AND active, AND at least one user with accounting manager or admin privileges can access the vulnerable REST API endpoint.

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 1.12.9
Interim mitigation

Update the WP ERP plugin to version 1.13.1 or later where the vendor has patched the SQL injection vulnerability by implementing proper parameter escaping and prepared statements.

Recommended fix Moderate confidence

Latest version after 1.13.0 (verify fixed version on wordpress.org/plugins/wp-erp)

  1. Check your current WP ERP plugin version under Plugins > Installed Plugins in WordPress admin
  2. Backup your WordPress database and files before any upgrade
  3. Navigate to Plugins > Installed Plugins > WP ERP and update to the latest version available
  4. Verify the update completed successfully by checking the version number
  5. Test that the accounting REST API endpoint (erp/v1/accounting/v1/transactions/sales) functions correctly after the update
  6. Ensure only trusted users with accounting manager or admin privileges have access to the accounting module
Caveat Review plugin changelog for any changes to accounting features or API behavior before upgrading in production

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

Fix this in Wp Erp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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