CVE-2024-0182
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 vulnerability was found in SourceCodester Engineers Online Portal 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /admin/ of the component Admin Login. The manipulation of the argument username/password leads to sql injection. The attack may be launched remotely. The identifier of this vulnerability is VDB-249440.
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 confidenceCritical SQL injection vulnerability in SourceCodester Engineers Online Portal 1.0 admin login at /admin/ endpoint. User-supplied username and password parameters are not properly sanitized, allowing remote attackers to inject malicious SQL queries and potentially gain unauthorized administrative access to the application 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Engineers Online Portal installationIdentify the web application's file structure in the web root. Look for directories or files associated with Engineers Online Portal, such as admin/ folder, login.php, or index.php files with portal-related naming.Affected if The Engineers Online Portal application files are present on the system
-
Verify application version is 1.0Search for version files, version constants in PHP files, README files, or any version metadata within the application directory. Check files like version.php, about.php, or config files for version = 1.0.Affected if The installed version is 1.0 exactly
-
Confirm admin login endpoint existsMake an HTTP request to the /admin/ path (e.g., /admin/, /admin/login.php, or /admin/index.php) to verify the admin login page is accessible.Affected if The admin login page at /admin/ endpoint is accessible and responds with a login form
-
Inspect login code for vulnerable SQL patternLocate the admin login processing script (typically login.php or auth.php in the admin directory). Open the file and examine how the username and password parameters are used in SQL queries. Look for direct concatenation of user input into SQL strings without prepared statements, parameter binding, or escaping functions.Affected if The login code constructs SQL queries by directly inserting the username and/or password parameters into the query string without using prepared statements or proper sanitization
If the Engineers Online Portal version 1.0 is present with an accessible /admin/ login endpoint that uses inline SQL queries with unsanitized user input for authentication, the environment is affected by CVE-2024-0182.
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 inline SQL queries with parameterized queries (prepared statements) in the admin login functionality. Apply input validation and implement proper output encoding. Check vendor for available patches.
- Consultation3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0182 — 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-0182 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