CVE-2024-33957
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 · uneditedSQL injection vulnerability in E-Negosyo System affecting version 1.0. An attacker could exploit this vulnerability by sending a specially crafted query to the server and retrieve all the information stored in 'id' in '/admin/orders/controller.php' parameter
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 E-Negosyo System v1.0 allows unauthenticated or authenticated attackers to inject malicious SQL queries through the 'id' parameter in /admin/orders/controller.php. Successful exploitation enables retrieval of sensitive data from the database.
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= 1.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm E-Negosyo System installationLocate the web application's root directory and check for the presence of index.php, admin/orders/controller.php, or other E-Negosyo System-specific files.Affected if The E-Negosyo System files are present in the web server directory.
-
Identify installed versionCheck the source code for version information, commonly found in files like about.php, version.php, README, or in comments within main PHP files. Look for '1.0' or 'version' strings.Affected if The installed version is exactly 1.0.
-
Verify vulnerable file existsCheck if /admin/orders/controller.php exists in the web application directory.Affected if The file /admin/orders/controller.php exists.
-
Check for vulnerable SQL query patternInspect /admin/orders/controller.php and search for SQL queries using the 'id' parameter without parameterized queries. Look for patterns like $_GET['id'] or $_POST['id'] directly in SQL statements.Affected if The code contains direct use of the 'id' parameter in SQL queries without prepared statements or input sanitization.
-
Test parameter vulnerabilitySend an HTTP request to /admin/orders/controller.php with a SQL injection payload in the 'id' parameter, such as 'id=1' OR '1'='1 or id=1' AND SLEEP(5)--. Observe the application's response for SQL errors or delayed responses.Affected if The application returns database errors, unexpected data, or experiences delay indicating SQL injection is possible.
A user is affected if they have E-Negosyo System v1.0 installed with the vulnerable /admin/orders/controller.php file present and the 'id' parameter accepts unsanitized input.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) and implement proper input validation on the 'id' parameter.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33957 — 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-33957 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