dbcve.org
Wp ErpWordPress extension · Wedevs

CVE-2024-0608

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to after 1.12.9 or later.
See remediation →
71/100
Remediation priority · Elevated
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 union-based SQL Injection via the 'email' parameter in all versions up to, and including, 1.13.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, 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 WordPress plugin is vulnerable to union-based SQL injection via the 'email' parameter in versions up to 1.13.1. The vulnerability stems from insufficient escaping of user-supplied input combined with lack of prepared statements in the SQL query, allowing authenticated attackers with subscriber-level access to inject malicious SQL queries and extract sensitive database information.

MitigationUpdate the WP ERP plugin to version 1.13.2 or later which contains the security patch. As a temporary measure, restrict user registration or disable the affected functionality until the update can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed WP ERP version
    Check the WordPress plugin directory (wp-content/plugins/wp-erp) for a readme.txt or index.php file containing the version number, or view the Plugins page in wp-admin dashboard
    Affected if Version is 1.12.9 or lower, or any version up to and including 1.13.1 (if the patch was not applied)
  2. Identify the vulnerable endpoint
    Locate the PHP file handling the 'email' parameter in ERP requests; typically found in includes/ or modules/ directories under wp-erp, specifically where user subscription or email-related forms process input
    Affected if The 'email' parameter is accepted directly in a SQL query without prepare() statement or proper escaping
  3. Verify user role access exists
    Check if subscriber-level accounts can be created on the WordPress site, or review the capability requirements for the affected ERP functionality (usually in the function handling the email parameter)
    Affected if Subscriber or any authenticated user role can access the vulnerable endpoint with the 'email' parameter
  4. Inspect the SQL query construction
    Review the code that processes the 'email' parameter in the identified PHP file; look for direct concatenation of $_POST['email'] or similar into a SQL query string
    Affected if The email value is concatenated into the SQL query without using $wpdb->prepare() or equivalent escaping

A user is affected if their installed WP ERP version is 1.12.9 or below (or unpatched 1.13.1) AND subscriber-level authentication is possible to reach the vulnerable 'email' parameter 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.2 or later which contains the security patch. As a temporary measure, restrict user registration or disable the affected functionality until the update can be applied.

Recommended fix High confidence

1.13.2 or latest stable release

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find WP ERP in the plugin list
  4. Check if an update is available
  5. If an update is available, click 'Update Now'
  6. Alternatively, download the latest version from wordpress.org/plugins/wp-erp/ and upload it manually via Plugins > Add New > Upload Plugin
  7. After updating, verify the 'email' parameter is now properly sanitized and prepared in SQL queries

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

Fix this in Wp Erp Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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