dbcve.org
InjectionWeakness · CWE-74

CVE-2025-10973

HIGH · 7.3 CVSS v3.1 Published 2025-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 flaw has been found in JackieDYH Resume-management-system up to fb6b857d852dd796e748ce30c606fe5e61c18273. Affected by this issue is some unknown functionality of the file /admin/show.php. This manipulation of the argument userid causes sql injection. The attack may be initiated remotely. The exploit has been published and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The vendor was contacted early about this disclosure but did not respond in any way.

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 JackieDYH Resume-management-system's /admin/show.php file. The userid parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code. The vulnerability is exploitable remotely and a proof-of-concept exploit is publicly available.

MitigationImplement parameterized queries or prepared statements for all database operations involving user input. Alternatively, deploy a web application firewall (WAF) as a temporary mitigation until code-level fixes can be implemented.

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
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 if JackieDYH Resume-management-system is present
    Search the web root directory for files named show.php in an /admin/ path, or look for application files containing 'Resume-management-system' or similar branding.
    Affected if The application files exist on the server.
  2. Determine the installed version
    Check for version information in the application source code, such as version.php, README files, or a meta tag in index pages. Compare against any version numbers found in the file headers or comments.
    Affected if The version cannot be determined or falls within an unknown range containing the vulnerability.
  3. Verify the vulnerable file exists
    Locate the /admin/show.php file within the application directory structure and confirm it exists.
    Affected if The file /admin/show.php exists in the application.
  4. Check if admin panel is exposed
    Attempt to access the /admin/show.php endpoint via HTTP from an untrusted network, or inspect the web server configuration to see if /admin/ paths are publicly accessible.
    Affected if The /admin/ interface is reachable without authentication or from external networks.
  5. Inspect the userid parameter handling
    Examine the source code of /admin/show.php to see if the userid parameter is used directly in SQL queries without prepared statements, parameterized queries, or input sanitization functions.
    Affected if The userid parameter is concatenated into SQL queries without proper escaping or parameter binding.

A user is affected if the JackieDYH Resume-management-system is installed, the /admin/show.php file exists, and the userid parameter is used in SQL queries without sanitization or prepared statements.

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 parameterized queries or prepared statements for all database operations involving user input. Alternatively, deploy a web application firewall (WAF) as a temporary mitigation until code-level fixes can be implemented.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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