dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2022-4984

HIGH · 8.7 CVSS v4.0 Published 2025-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
ZenTao Biz < 6.5, ZenTao Max < 3.0, ZenTao Open Source Edition < 16.5, and ZenTao Open Source Edition < 16.5.beta1 contain an SQL injection vulnerability in the login functionality. The application does not properly validate the account parameter on /zentao/user-login.html before using it in a database query. A remote unauthenticated attacker can exploit this issue to execute crafted SQL expressions and retrieve sensitive information from the backend database, including user and application data. Exploitation evidence was observed by the Shadowserver Foundation on 2025-02-07 UTC.

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 ZenTao project management software's login functionality. The account parameter on /zentao/user-login.html is not properly validated before being used in database queries, allowing remote unauthenticated attackers to inject malicious SQL code and extract sensitive data.

MitigationApply vendor patches for affected ZenTao versions (Biz < 6.5, Max < 3.0, Open Source < 16.5). If immediate patching is not feasible, implement WAF rules or temporary input validation controls to block SQL injection payloads in the account parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify ZenTao version
    Check the version.php file in the ZenTao installation directory, or access the /zentao/api-getsessionid.html endpoint which returns version info in the response. Alternatively, check the footer of any ZenTao page for the version number.
    Affected if The installed version is Biz < 6.5, Max < 3.0, or Open Source < 16.5
  2. Confirm login endpoint is accessible
    Access the URL /zentao/user-login.html in a web browser or via curl. Verify the page loads and contains a login form with an account parameter input field.
    Affected if The login page is accessible without authentication and contains an account parameter field
  3. Verify SQL injection is possible
    Send a test request to /zentao/user-login.html with a benign SQL payload in the account parameter (e.g., account=admin' AND '1'='1) and observe if the application returns different responses compared to a normal request. Use error-based detection by checking for SQL syntax error messages in the response.
    Affected if The application returns SQL error messages or exhibits different behavior when SQL syntax is injected into the account parameter, indicating the input is not properly sanitized before being used in database queries

A user is affected if ZenTao is running an unpatched version (Biz < 6.5, Max < 3.0, Open Source < 16.5) AND the login page at /zentao/user-login.html is accessible with an account parameter that does not sanitize SQL syntax.

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

Apply vendor patches for affected ZenTao versions (Biz < 6.5, Max < 3.0, Open Source < 16.5). If immediate patching is not feasible, implement WAF rules or temporary input validation controls to block SQL injection payloads in the account parameter.

Recommended fix High confidence

ZenTao Biz 6.5, ZenTao Max 3.0, or ZenTao Open Source Edition 16.5 (depending on edition in use)

  1. 1. Back up the current ZenTao installation and database before any upgrade
  2. 2. Identify which ZenTao edition is in use (Biz, Max, or Open Source Edition)
  3. 3. Download the corresponding fixed version: ZenTao Biz 6.5, ZenTao Max 3.0, or ZenTao Open Source Edition 16.5
  4. 4. Follow the official ZenTao upgrade guide to install the fixed version
  5. 5. Verify the login functionality at /zentao/user-login.html works correctly
  6. 6. Confirm the SQL injection vulnerability is no longer exploitable by testing with malicious input in the account parameter
Caveat Review ZenTao upgrade documentation for version-specific migration notes and potential configuration changes between major versions

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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