dbcve.org
InjectionWeakness · CWE-74

CVE-2025-14568

MEDIUM · 6.3 CVSS v3.1 Published 2025-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 security vulnerability has been detected in haxxorsid Stock-Management-System up to fbbbf213e9c93b87183a3891f77e3cc7095f22b0. This impacts an unknown function of the file model/User.php. The manipulation of the argument employee_id/id/admin leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way. This vulnerability only affects products that are no longer supported by the maintainer.

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 haxxorsid Stock-Management-System's User.php model file. The employee_id/id/admin parameters are not properly sanitized, allowing attackers to inject malicious SQL queries remotely. The exploit has been publicly disclosed.

MitigationImplement prepared statements/parameterized queries to sanitize user inputs, particularly for employee_id/id/admin parameters in User.php. Consider migrating to a supported version or alternative solution since the product is no longer maintained.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 haxxorsid Stock-Management-System is installed
    Search the web root or application directory for files containing 'Stock-Management-System' branding, or look for the User.php file in models/ application directories
    Affected if The application directory contains a Stock-Management-System codebase with a User.php model file
  2. Locate the vulnerable User.php model file
    Navigate to the application models directory and confirm the presence of User.php
    Affected if User.php exists in the application's models or model directory
  3. Inspect the employee_id, id, and admin parameter handling in User.php
    Open User.php and search for occurrences of 'employee_id', 'id', or 'admin' parameters in query-building code (SELECT, UPDATE, DELETE, INSERT statements)
    Affected if The code contains SQL queries that directly incorporate these parameters without visible sanitization or prepared statement placeholders
  4. Verify if raw SQL concatenation or string interpolation is used
    Look for patterns like $this->db->query("SELECT..." . $id) or similar string concatenation where user-supplied parameters are appended to SQL strings
    Affected if SQL queries concatenate or interpolate these parameters directly into query strings without binding or escaping functions
  5. Confirm remote accessibility of the application
    Determine if the application is accessible over a network (HTTP/HTTPS) to external users, as this is a remote SQL injection
    Affected if The application is exposed to network requests from untrusted sources without authentication barriers

If the User.php file exists and contains SQL queries using direct parameter concatenation for employee_id, id, or admin without prepared statements, the environment is vulnerable to CVE-2025-14568.

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 to sanitize user inputs, particularly for employee_id/id/admin parameters in User.php. Consider migrating to a supported version or alternative solution since the product is no longer maintained.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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