dbcve.org
Employee Task Management SystemApplication · Oretnom23

CVE-2024-2574

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 classified as critical was found in SourceCodester Employee Task Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /edit-task.php. The manipulation of the argument task_id leads to authorization bypass. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-257077 was 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

Critical authorization bypass vulnerability in SourceCodester Employee Task Management System 1.0's /edit-task.php. The task_id parameter is not properly validated, allowing unauthenticated or unauthorized remote attackers to manipulate it and bypass authorization checks to edit arbitrary tasks. The public exploit availability and CVSS 9.8 indicate immediate exploitation risk.

MitigationImplement proper server-side authorization checks in edit-task.php to verify the authenticated user owns or has permission to modify the specific task_id. Validate that the task belongs to the requesting user and enforce session-based access controls.

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 the Employee Task Management System version
    Locate the application files and check the version number in the source code, typically found in an about page, README file, or version configuration. Compare your installed version to 1.0.
    Affected if The installed version is exactly 1.0.
  2. Verify edit-task.php exists in the application
    Locate the edit-task.php file within the web application directory structure. This is the file containing the vulnerable code.
    Affected if The file edit-task.php exists in the web application's document root or source directory.
  3. Check if the application is network-accessible
    Determine whether the web server hosting the Employee Task Management System is accessible over the network (internal or external). Attempt to access the login or main page from an unauthorized host.
    Affected if The application is reachable from network hosts without authentication.
  4. Examine task_id parameter handling in edit-task.php
    Open edit-task.php and inspect the code that processes the task_id parameter. Look for server-side authorization logic that verifies the authenticated user owns or has permission to modify the specific task.
    Affected if The task_id parameter is processed without verifying that the requesting user owns the task or has permission to edit it.
  5. Check for session-based access control enforcement
    In edit-task.php, verify whether session-based access controls are implemented before allowing task modifications. Look for code that validates the user session and correlates it with the requested task_id.
    Affected if No session validation or user-task ownership check exists before allowing task edits.

You are affected if the Employee Task Management System version 1.0 is installed, edit-task.php is present, and the task_id parameter lacks proper authorization checks to verify user ownership of the task.

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 server-side authorization checks in edit-task.php to verify the authenticated user owns or has permission to modify the specific task_id. Validate that the task belongs to the requesting user and enforce session-based access controls.

Fix this in Employee Task Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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