dbcve.org
Employee Task Management SystemApplication · 1000projects

CVE-2025-0846

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-30
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 was found in 1000 Projects Employee Task Management System 1.0. It has been classified as critical. This affects an unknown part of the file /admin/AdminLogin.php. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack 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 the AdminLogin.php file of the 1000 Projects Employee Task Management System 1.0. The email parameter is not properly sanitized before being used in database queries, allowing remote attackers to inject arbitrary SQL commands. This could enable authentication bypass, data exfiltration, or complete database compromise.

MitigationImplement prepared statements/parameterized queries for all database interactions involving user input, specifically the email parameter in AdminLogin.php. Additionally, apply input validation and output encoding as defense-in-depth measures.

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. Verify the Employee Task Management System version
    Locate any version file, about page, or admin panel footer that displays the software version. Compare it to version 1.0.
    Affected if The installed version is exactly 1.0 of the 1000projects Employee Task Management System.
  2. Confirm the vulnerable login file exists
    Check if the file /admin/AdminLogin.php exists in the web root directory of the application.
    Affected if The file /admin/AdminLogin.php is present on the server.
  3. Inspect the email parameter handling in the login code
    Open /admin/AdminLogin.php and examine how the email POST parameter is handled before being used in SQL queries. Look for direct concatenation or lack of prepared statements.
    Affected if The email parameter is used directly in SQL queries without parameterized queries, prepared statements, or input sanitization.
  4. Determine if the admin panel is network-accessible
    Attempt to access the login page at /admin/AdminLogin.php via HTTP/HTTPS from a browser or curl command.
    Affected if The vulnerable login page is accessible over the network.
  5. Check for lack of input validation in SQL query construction
    Review the SQL query code in AdminLogin.php for the email field - look for patterns like $email directly inserted into the query string without escaping or binding.
    Affected if The code constructs SQL queries by directly inserting the email variable without escaping, binding, or validation functions.

A user is affected if they are running Employee Task Management System version 1.0 with the /admin/AdminLogin.php file accessible and the email parameter handled without prepared statements in the SQL queries.

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 prepared statements/parameterized queries for all database interactions involving user input, specifically the email parameter in AdminLogin.php. Additionally, apply input validation and output encoding as defense-in-depth measures.

Fix this in Employee Task Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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