CVE-2025-13395
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 security flaw has been discovered in codehub666 94list up to 5831c8240e99a72b7d3508c79ef46ae4b96befe8. The impacted element is the function Login of the file /function.php. The manipulation results in sql injection. The attack can be launched remotely. The exploit has been released to the public and may be exploited. This product does not use versioning. This is why information about affected and unaffected releases are unavailable.
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 confidenceA SQL injection vulnerability exists in the Login function of /function.php in codehub666 94list (up to commit 5831c824). The vulnerability is remotely exploitable, has a public exploit, and stems from unsanitized user input being incorporated directly into SQL queries. The lack of versioning prevents determining whether patches exist.
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.
-
Check the git commit version of the 94list installationRun 'git log --oneline -1' in the project root directory to obtain the current commit hashAffected if The commit hash is 5831c824 or earlier (the vulnerability exists up to this commit)
-
Locate the function.php fileVerify the presence of /function.php in the web root or application directory of the 94list installationAffected if The file exists and is part of the active codebase
-
Inspect the Login function for SQL injection vulnerabilityOpen /function.php and locate the 'function login' or 'function user_login' function definition. Examine the SQL query construction within this function for direct concatenation of user-supplied input (such as username or password variables) into the query stringAffected if User input from POST/GET parameters is directly concatenated into SQL queries without using prepared statements, parameterized queries, or input sanitization functions
-
Identify the vulnerable SQL query patternSearch for patterns like $sql = "SELECT...WHERE username = '$username'" or similar dynamic SQL construction in the Login function. Check if $_POST or $_GET superglobals are used directly in the query without escaping or bindingAffected if The Login function contains SQL queries where $_POST, $_GET, or similar user-supplied variables are embedded directly into the query string without escaping or parameter binding
If the installation is at commit 5831c824 or earlier, or if the Login function in /function.php contains direct string concatenation of user input into SQL queries, the system is vulnerable to SQL injection.
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 dataReplace dynamic SQL queries in the Login function with parameterized queries/prepared statements to neutralize injection vectors. If immediate patching is not possible, implement input validation and web application firewall rules as a temporary compensating control.
- 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-13395 — 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-13395 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