CVE-2024-42844
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 · uneditedA SQL Injection vulnerability has been identified in EPICOR Prophet 21 (P21) up to 23.2.5232. This vulnerability allows authenticated remote attackers to execute arbitrary SQL commands through unsanitized user input fields to obtain unauthorized information
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 confidenceSQL injection vulnerability in EPICOR Prophet 21 (P21) versions up to 23.2.5232 allows authenticated remote attackers to execute arbitrary SQL commands through unsanitized user input fields, potentially enabling unauthorized data exfiltration.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm EPICOR Prophet 21 installationCheck system inventory or installed programs for EPICOR Prophet 21 or P21 software. Look for Prophet 21 executables, services, or web application directories on the server.Affected if Prophet 21 or P21 is installed on the system
-
Identify installed Prophet 21 versionAccess the Prophet 21 application or system information panel, typically found in the software About section, registry keys under HKLM\SOFTWARE\Epicor\Prophet21, or the P21 web application version file.Affected if The installed version is 23.2.5232 or any earlier version (versions prior to the patch for this CVE)
-
Verify web interface accessibilityCheck if the P21 web interface (typically accessed via IIS or the built-in web server on ports 80/443 or custom ports) is exposed and accessible from network locations.Affected if The P21 web interface is reachable over the network to authenticated users
-
Confirm user authentication is enabledReview the Prophet 21 authentication configuration to verify that user login functionality is active, allowing authenticated users to access input fields within the application.Affected if User authentication is enabled and user accounts can log in to access application features
-
Identify user input fields in useCatalog user-facing input forms within the P21 web application, particularly search fields, data entry forms, or any parameter-driven pages that accept user-supplied values.Affected if User input fields are present and accessible to authenticated users in the application
You are affected if EPICOR Prophet 21 (P21) is installed with version 23.2.5232 or earlier and the web interface with user authentication is accessible to users who can supply input to application fields.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries or prepared statements for all database interactions involving user input; apply vendor patch when available; conduct input validation audit across all user-facing fields.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-42844 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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