dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-13011

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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 ERP: Complete HR, Accounting & CRM Suite with Recruitment and WooCommerce CRM Support plugin for WordPress is vulnerable to generic SQL Injection via the 'orderby' parameter in all versions up to, and including, 1.17.5 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 custom-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires the erp_list_employee capability, which is granted to HR Manager-level users and above within the WP ERP plugin.

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 WordPress WP ERP plugin fails to properly escape the 'orderby' parameter and lacks prepared statements in SQL queries, allowing authenticated users with HR Manager-level access (erp_list_employee capability) to inject arbitrary SQL commands and extract sensitive database information.

MitigationUpdate the plugin to version 1.17.6 or later which addresses the SQL injection vulnerability in the 'orderby' parameter handling.

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

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. Confirm WP ERP plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'WP ERP' in the list, or inspect the file /wp-content/plugins/wp-erp directory and check the main plugin file header for the Version field
    Affected if The plugin is present and active in the WordPress installation
  2. Determine installed WP ERP version
    Read the plugin version from the plugin header in the main plugin file (typically wp-erp.php) or from the WordPress plugin administration screen
    Affected if The installed version is earlier than 1.17.6 (versions prior to 1.17.6 are vulnerable)
  3. Verify HR Manager role or erp_list_employee capability exists
    Check WordPress user roles and capabilities: use a user role editor plugin, query the wp_options table for 'wp_user_roles', or inspect the WP ERP code for 'erp_list_employee' capability registration. Look for users assigned the HR Manager role
    Affected if Any user account possesses the HR Manager role or erp_list_employee capability, enabling access to the vulnerable endpoint
  4. Identify access to employee listing with orderby parameter
    Locate the employee listing endpoint in WP ERP (typically under WP ERP > HR > Employees). Inspect the request handling code for the 'orderby' parameter usage, particularly in SQL queries without prepared statements. Common vulnerable path: /wp-admin/admin.php?page=erp-hr&section=employee&orderby=...
    Affected if The HR Manager capability is present AND the employee listing feature is accessible, allowing the vulnerable 'orderby' parameter to be manipulated

A user is affected if WP ERP version is below 1.17.6 AND an account with HR Manager role (erp_list_employee capability) exists with access to the employee listing functionality where the orderby parameter can be exploited.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.17.6 or later which addresses the SQL injection vulnerability in the 'orderby' parameter handling.

Recommended fix Moderate confidence

Any version greater than 1.17.5 of the WP ERP plugin

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'ERP: Complete HR, Accounting & CRM Suite with Recruitment and WooCommerce CRM Support' plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin version is greater than 1.17.5

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

Have this fixed 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 help mitigating

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-2026-13011 — 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-2026-13011 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