CVE-2025-10967
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 · uneditedA vulnerability was detected in MuFen-mker PHP-Usermm up to 37f2d24e51b04346dfc565b93fc2fc6b37bdaea9. This affects an unknown part of the file /chkuser.php. Performing manipulation of the argument Username results in sql injection. The attack may be initiated remotely. The exploit is now public 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 confidenceSQL injection vulnerability in MuFen-mker PHP-Usermm's /chkuser.php file allows remote attackers to inject malicious SQL queries via the Username parameter. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized data access or data manipulation.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify MuFen-mker PHP-Usermm installationSearch your web root directories for the presence of the MuFen-mker PHP-Usermm application files, particularly looking for directories containing 'usermm' or 'mufen' in the nameAffected if The application is present in your environment
-
Locate the vulnerable chkuser.php fileCheck for the file chkuser.php within the usermm or application directory structure - typically found in the application's root or includes folderAffected if The file /chkuser.php exists in your installation
-
Verify the Username parameter handlingExamine the chkuser.php source code and search for SQL query construction involving the 'Username' parameter without prepared statements or parameterizationAffected if The code uses the Username parameter directly in SQL queries without escaping or prepared statements (look for patterns like "SELECT...WHERE username='$Username'" or "...username=" . $_POST['Username'])
-
Confirm external access to the vulnerable endpointDetermine if chkuser.php is accessible via HTTP/HTTPS without authentication - check if the file is reachable from the web and does not require login to accessAffected if The chkuser.php endpoint is accessible externally without authentication
You are affected if MuFen-mker PHP-Usermm is installed, the chkuser.php file exists, and the Username parameter is used in SQL queries without prepared statements or input sanitization and is accessible to attackers
Generated from the published advisory. Verify against your own configuration.
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 dataImplement prepared statements/parameterized queries for all database operations involving user input. Alternatively, implement strict input validation and sanitization on the Username parameter before using it in SQL queries.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10967 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10967 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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