CVE-2024-35468
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 in /hrm/index.php in SourceCodester Human Resource Management System 1.0 allows attackers to execute arbitrary SQL commands via the password 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 SourceCodester HRMS 1.0 login page (/hrm/index.php) allows attackers to inject malicious SQL commands through the password parameter, potentially enabling unauthorized access to the database, data exfiltration, or data manipulation.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 SourceCodester HRMS installationLocate the web application directory and identify if it contains the HRMS system. Look for files named 'index.php' within an '/hrm' directory or subdirectory.Affected if The application is installed in a web-accessible directory and contains SourceCodester/Oretnom23 HRMS files.
-
Verify the application version is 1.0Check for version indicators such as a version.php file, footer/about page, or any file containing 'version 1.0' or 'v1.0'. Common locations include /includes/, /config/, or the main index.php file.Affected if The installed version is exactly 1.0.
-
Identify the vulnerable login scriptLocate the file /hrm/index.php in the webroot. This is the login page where the SQL injection vulnerability exists in the password parameter handling.Affected if The file /hrm/index.php exists and is accessible as the application's login page.
-
Inspect SQL query implementation in login codeOpen /hrm/index.php and search for the SQL query that processes the login password. Look for query construction that uses string concatenation or direct insertion of the $_POST['password'] variable into the SQL statement.Affected if The login code uses direct string concatenation to build SQL queries with the password parameter instead of parameterized queries or prepared statements.
You are affected if you have SourceCodester/Oretnom23 HRMS version 1.0 installed with the /hrm/index.php login page that uses non-parameterized SQL queries for password authentication.
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 string concatenation in SQL queries with parameterized queries/prepared statements for all user inputs, particularly the password parameter. Apply input validation and enforce least privilege database accounts.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35468 — 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-35468 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