dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-9977

MEDIUM · 5.3 CVSS v4.0 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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
Value provided in one of POST parameters sent during the process of logging in to Times Software E-Payroll is not sanitized properly, which allows an unauthenticated attacker to perform DoS attacks. SQL injection attacks might also be feasible, although so far creating a working exploit has been prevented probably by backend filtering mechanisms. Additionally, command injection attempts cause the application to return extensive error messages disclosing some information about the internal infrastructure.  Patching status is unknown because the vendor has not replied to messages sent by the CNA.

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

Times Software E-Payroll has unsanitized POST parameters in its login process, enabling unauthenticated attackers to cause denial of service. While SQL injection may be blocked by backend filters, the lack of input sanitization combined with verbose error messages on command injection attempts creates information disclosure risks about the internal infrastructure.

MitigationSince no vendor patch is available, implement compensating controls such as Web Application Firewall rules to filter malicious input, rate limiting to mitigate DoS, and configure application servers to return generic error messages instead of detailed stack traces.

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
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/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. Confirm Times Software E-Payroll installation
    Search for Times Software E-Payroll application files in web server document roots or application directories. Common paths may include /var/www/, /inetpub/, or application-specific directories. Look for files named 'login', 'epayroll', or Times Software branding.
    Affected if The application is present on the system
  2. Identify the installed version
    Locate version information in the application. Check for version.txt, About pages within the E-Payroll web interface, or configuration files that may contain version strings. Compare against any publicly documented version numbers for this product.
    Affected if The installed version cannot be determined or is earlier than any patched version
  3. Verify login endpoint accessibility
    Access the login page via HTTP/HTTPS. Confirm the login form processes POST requests to the authentication endpoint. Note the URL path used for credential submission.
    Affected if The login form is accessible without authentication and accepts POST parameters
  4. Inspect error message configuration
    Examine application configuration files and application server settings for error handling. Check if custom error pages are configured or if the application returns detailed stack traces and system information in error responses.
    Affected if Verbose error messages, stack traces, or infrastructure details are returned to unauthenticated users
  5. Test for input validation in login parameters
    Submit a benign test payload (such as a simple string with special characters) to the login POST parameters. Observe whether the application returns detailed error messages, executes any injected input, or crashes causing denial of service.
    Affected if The application reflects submitted input in error messages, throws unhandled exceptions, or becomes unresponsive

A user is affected if Times Software E-Payroll is installed with an accessible login form that returns verbose error messages without sanitizing POST parameter input.

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

Since no vendor patch is available, implement compensating controls such as Web Application Firewall rules to filter malicious input, rate limiting to mitigate DoS, and configure application servers to return generic error messages instead of detailed stack traces.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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