# CVE-2024-0913: WP ERP <= 1.13.0 - Authenticated (Accounting Manager+) SQL Injection

> Authenticated attackers with accounting manager privileges can exploit SQL injection to extract sensitive database information via the sales transactions API.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-v8cq-w557-hfjg

## What is CVE-2024-0913?

CVE-2024-0913 is a high-severity SQL injection vulnerability in wedevs ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support, published on 29 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-0913?

It affects 1 product.


Products: Wedevs Wp Erp.

## How do I fix CVE-2024-0913?

No fix has been published for CVE-2024-0913 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-0913 being exploited?

There is no known exploitation of CVE-2024-0913 in the wild and no public exploit code.

## Other vulnerabilities in wedevs ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support

- [CVE-2024-6666](https://insights.sbomify.com/CVE-2024-6666/): WP ERP <= 1.13.0 - Authenticated (Accounting Manager+) SQL Injection via vendor_id (high 8.8)
- [CVE-2024-21747](https://insights.sbomify.com/CVE-2024-21747/): WordPress WP ERP Plugin <= 1.12.8 is vulnerable to SQL Injection (high 7.6)
- [CVE-2024-12812](https://insights.sbomify.com/CVE-2024-12812/): WP ERP < 1.13.4 - Custom+ Unauthorized Access to Terminated Employee Information (high 7.5)
- [CVE-2024-1173](https://insights.sbomify.com/CVE-2024-1173/): SQL injection in ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support (high 7.2)
- [CVE-2024-0952](https://insights.sbomify.com/CVE-2024-0952/): WP ERP <= 1.12.9 - Authenticated (Accounting Manager+) SQL Injection via id (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0913 and fix it if it is affected.

What it is: CVE-2024-0913 is a high-severity SQL injection vulnerability in wedevs ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support, published on 29 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0913 in the wild and no public exploit code.

Affected product: wedevs ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-0913/ (Markdown: https://insights.sbomify.com/CVE-2024-0913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-0913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-0913
- OSV: https://osv.dev/vulnerability/CVE-2024-0913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-0913/
Summaries are generated and may contain mistakes; the official description above is the record.