CVE-2025-11654
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 identified in yousaf530 Inferno Online Clothing Store up to 827dd42bfbe380e8de76fdc67958c24cf1246208. The affected element is an unknown function of the file /log.php. Such manipulation of the argument cemail/password leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are 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 /log.php allows remote attackers to inject malicious SQL commands through the cemail and password parameters, potentially enabling authentication bypass, data exfiltration, or database compromise.
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.
-
Locate the log.php fileSearch the webroot for the file /log.php using file system search (e.g., 'find /var/www -name log.php' or locate log.php in the application directory)Affected if The file /log.php exists in the application and handles user authentication
-
Inspect parameter handlingOpen /log.php and search for occurrences of 'cemail' and 'password' variables (e.g., $_POST['cemail'], $_GET['cemail'], $_REQUEST['cemail'])Affected if The file processes cemail and password as user input without validation
-
Analyze SQL query constructionSearch for SQL query patterns in /log.php that include cemail/password variables directly in query strings (look for SELECT, INSERT, UPDATE statements containing these parameters)Affected if SQL queries concatenate or interpolate cemail/password directly into the query string without using prepared statements or parameter binding
-
Verify database layer usageCheck if the code uses database functions without parameterized queries (look for mysql_query, mysqli_query, $pdo->query without prepare() and bindParam/bindValue)Affected if Database queries involving cemail/password are executed without prepared statements or input sanitization
-
Test parameter injectionIf testing is authorized, submit a single quote (') in the cemail or password parameter to the login form and observe database error messages in the responseAffected if Submitting a single quote produces a database syntax error or unexpected behavior indicating unsanitized input is passed to SQL
A user is affected if /log.php exists, accepts cemail/password parameters, and constructs SQL queries by directly inserting these parameters into query strings without prepared statements or proper escaping.
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 in /log.php for all database queries involving user input (cemail/password), or sanitize input using whitelisting and proper escaping functions.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11654 — 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-11654 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