dbcve.org
Employee Profile Management SystemApplication · Code Projects

CVE-2024-0466

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-12
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, which was classified as critical, has been found in code-projects Employee Profile Management System 1.0. This issue affects some unknown processing of the file file_table.php. The manipulation of the argument per_id leads to sql injection. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-250571.

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

SQL injection vulnerability in the Employee Profile Management System 1.0 file_table.php script allows remote attackers to inject malicious SQL queries via the 'per_id' parameter. With a CVSS 9.8 critical rating and publicly available exploit, this vulnerability is easily exploitable and could lead to complete database compromise including data exfiltration or destruction.

MitigationImplement parameterized queries (prepared statements) for all database operations using the per_id parameter, or apply proper input validation and escaping. Apply immediate network-level restrictions to limit exposure until the code fix is deployed.

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
Employee Profile Management 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 Employee Profile Management System is installed
    Identify the web application in your environment. Look for directories or files related to 'Employee Profile Management System' or 'Employee Profile' in your web root. Check for login pages or administrative interfaces specific to this system.
    Affected if The application is present in your environment and is version 1.0 of Code Projects Employee Profile Management System
  2. Locate file_table.php script
    Search your web server directories for the file 'file_table.php'. This is the vulnerable script mentioned in the CVE. Check within the application's main directory structure.
    Affected if The file file_table.php exists and is accessible via the web server
  3. Verify installed version is 1.0
    Check the application's version information. Look for version numbers in source files, configuration files, or the application's about/info page. Compare against the affected version range (= 1.0).
    Affected if The installed version is exactly 1.0 (or if the version cannot be determined and the application appears to be this system)
  4. Confirm database connectivity is in use
    Since this is a SQL injection vulnerability, verify the application is configured to use a database (MySQL, MariaDB, or similar). Check configuration files for database connection strings or credentials.
    Affected if The application has an active database connection configured and accessible
  5. Identify if per_id parameter is processed without protection
    Examine the file_table.php source code to see how the 'per_id' parameter is handled. Look for direct inclusion of this parameter in SQL queries without prepared statements, parameter binding, or input sanitization.
    Affected if The per_id parameter is used in SQL queries without parameterized queries or proper escaping

You are affected if Employee Profile Management System version 1.0 is installed, file_table.php exists and is accessible, and the per_id parameter in that file is processed in SQL queries without prepared statement protection.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database operations using the per_id parameter, or apply proper input validation and escaping. Apply immediate network-level restrictions to limit exposure until the code fix is deployed.

Fix this in Employee Profile Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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