dbcve.org
St. Joe Erp SystemApplication · St. Joe Erp System Project

CVE-2024-13979

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
A SQL injection vulnerability exists in the St. Joe ERP system ("圣乔ERP系统") that allows unauthenticated remote attackers to execute arbitrary SQL commands via crafted HTTP POST requests to the login endpoint. The application fails to properly sanitize user-supplied input before incorporating it into SQL queries, enabling direct manipulation of the backend database. Successful exploitation may result in unauthorized data access, modification of records, or limited disruption of service. An affected version range is undefined. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-04-14 UTC.

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

A critical SQL injection vulnerability exists in the St. Joe ERP login endpoint where user-supplied input from HTTP POST requests is directly concatenated into SQL queries without sanitization or parameterization. Unauthenticated attackers can manipulate query logic to execute arbitrary SQL commands, potentially gaining full database access or disrupting service.

MitigationImplement parameterized queries (prepared statements) for all database operations at the login endpoint, apply input validation and output encoding, and consider deploying a WAF as a temporary compensating control until code fixes are deployed.

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
St. Joe Erp SystemApplication
Affected:all versions

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 St. Joe ERP installation
    Locate the St. Joe ERP web application files on your server. Search for typical ERP directory structures or check your web server configuration for applications named 'St. Joe ERP' or similar.
    Affected if The software is present on your system.
  2. Identify login endpoint exposure
    Check your web server configuration (IIS, Apache, Nginx) for mappings to the St. Joe ERP application. Verify if the login endpoint (typically /login, /Login, or similar) is accessible over HTTP/HTTPS.
    Affected if The login endpoint is accessible from the network.
  3. Locate login source code
    Access the St. Joe ERP source code or decompile the application binaries. Search for the login handler function that processes HTTP POST requests, typically found in files like LoginController, AuthController, or similar naming conventions.
    Affected if You can locate the login processing code.
  4. Inspect SQL query construction in login logic
    Examine the login code for SQL query formation. Look for patterns where request parameters (username, password, or similar fields) are concatenated directly into SQL strings without using parameterized queries or prepared statements.
    Affected if User-supplied input from the login form is concatenated directly into SQL queries without sanitization or parameterization.
  5. Review database query logs
    Enable and review database query logging. Monitor SQL queries generated during login attempts. Look for malformed or unexpected SQL syntax that might indicate injection attempts or vulnerable query construction.
    Affected if Queries show direct string concatenation of user input into SQL commands.

If St. Joe ERP is installed and its login endpoint is accessible, you are affected because the login code concatenates user input directly into SQL queries without parameterization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database operations at the login endpoint, apply input validation and output encoding, and consider deploying a WAF as a temporary compensating control until code fixes are deployed.

Fix this in St. Joe Erp System Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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