dbcve.org
Employee Task Management SystemApplication · Oretnom23

CVE-2024-2575

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-18
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 SourceCodester Employee Task Management System 1.0. Affected by this issue is some unknown functionality of the file /task-details.php. The manipulation of the argument task_id leads to authorization bypass. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-257078 is the identifier assigned to this vulnerability.

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 confidence

A critical authorization bypass vulnerability exists in SourceCodester Employee Task Management System 1.0 within the /task-details.php file. By manipulating the task_id parameter, an attacker can potentially access or modify task information without proper authorization, allowing unauthorized viewing or alteration of sensitive employee task data.

MitigationImplement proper authentication and authorization checks on /task-details.php to verify the requesting user has legitimate access to the specific task_id being requested. All user sessions should be validated before returning any task data.

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 Task 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 Task Management System version
    Check the application version by inspecting the source code, configuration files, or footer of the web application. Look for version identifiers in files such as index.php, config.php, or any README/setup files included with the software.
    Affected if The installed version is exactly 1.0 as listed in the affected versions.
  2. Locate the vulnerable endpoint file
    Search for the presence of task-details.php in the web root directory or accessible paths of the application installation.
    Affected if The file /task-details.php exists in the application directory structure.
  3. Verify if the endpoint is accessible without authentication
    Attempt to access the task-details.php page directly via HTTP request (for example, by navigating to http://your-server/task-details.php or http://your-server/task-details.php?task_id=1) without providing valid session credentials.
    Affected if The page loads or returns a response without requiring authentication or session validation.
  4. Check task_id parameter authorization logic
    Examine the source code of task-details.php to determine whether the task_id parameter is validated against the currently authenticated user's permissions or ownership before returning task data.
    Affected if The code lacks proper authorization checks that verify the requesting user owns or has access to the specific task_id being requested.

The environment is affected if the installed Employee Task Management System is version 1.0, the task-details.php file exists, and the application does not properly validate user authorization before returning task data based on the task_id parameter.

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 proper authentication and authorization checks on /task-details.php to verify the requesting user has legitimate access to the specific task_id being requested. All user sessions should be validated before returning any task data.

Fix this in Employee Task Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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