dbcve.org
Attendance And Payroll SystemApplication · Nurhodelta17

CVE-2024-10421

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-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
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 vulnerability classified as critical was found in SourceCodester Attendance and Payroll System 1.0. This vulnerability affects unknown code of the file /admin/overtime_row.php. The manipulation of the argument id leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

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 confidence

A SQL injection vulnerability exists in SourceCodester Attendance and Payroll System 1.0 within the /admin/overtime_row.php file. The 'id' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL syntax. With a CVSS score of 9.8 (Critical), successful exploitation could allow complete database compromise including exfiltration of sensitive employee payroll data.

MitigationImplement prepared statements/parameterized queries for all database operations in overtime_row.php, or apply input validation and escaping for the id parameter. Additionally, apply the principle of least privilege to the database account used by the application.

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
Attendance And Payroll SystemApplication
Affected:= 1.0

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 installed version is 1.0
    Locate the application version file or check the application footer/about page for the version number. Compare against the affected range (1.0).
    Affected if The application version is exactly 1.0 (Nurhodelta17 Attendance and Payroll System)
  2. Verify overtime_row.php exists in admin directory
    Check for the presence of the file /admin/overtime_row.php in the web root directory of the application.
    Affected if The file /admin/overtime_row.php exists in the deployed application
  3. Confirm admin panel is accessible
    Attempt to access the admin login page and verify authentication is possible (via /admin/ or /admin/login.php).
    Affected if The admin panel is accessible and accepts authentication
  4. Check if id parameter handling is vulnerable
    Review the source code of overtime_row.php and locate the line where the 'id' parameter is used in SQL queries. Verify that prepared statements or input sanitization are NOT implemented for this parameter.
    Affected if The 'id' parameter is directly concatenated into SQL queries without sanitization or parameterization

You are affected if you are running version 1.0 of the Nurhodelta17 Attendance and Payroll System and the /admin/overtime_row.php file exists with the 'id' parameter vulnerable to SQL injection.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations in overtime_row.php, or apply input validation and escaping for the id parameter. Additionally, apply the principle of least privilege to the database account used by the application.

Recommended fix Moderate confidence
  1. Locate the vulnerable file /admin/overtime_row.php in the application directory
  2. Review the code handling the 'id' parameter to identify the unsanitized SQL query
  3. Replace the vulnerable SQL query with a prepared statement (using PDO or mysqli) that binds the 'id' parameter
  4. Ensure all user input is properly validated before use in SQL queries
  5. Test the fix by attempting the original exploit vector to confirm the vulnerability is remediated
  6. Apply the same SQL injection remediation to any other files in the application that may have similar vulnerabilities
Caveat No official fixed version available from the vendor; remediation requires direct code-level patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Attendance And Payroll System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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