CVE-2026-11471
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 found in SourceCodester Class and Exam Timetabling System 1.0. The impacted element is an unknown function of the file /index2.php. The manipulation of the argument Password results in sql injection. It is possible to launch the attack remotely. The exploit has been made public and could be used.
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 SourceCodester Class and Exam Timetabling System 1.0 allows remote attackers to inject malicious SQL queries via the Password parameter in /index2.php, potentially enabling authentication bypass or unauthorized data extraction.
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 the vulnerable endpointLocate the /index2.php file in your web root directory and confirm it contains a login form that accepts a Password parameterAffected if The file exists and contains a login form with a Password parameter that is used in SQL queries without sanitization
-
Verify SQL query usageInspect the source code of /index2.php and locate the SQL query that processes the Password parameter. Look for direct concatenation of user input into the query stringAffected if The Password parameter is directly concatenated into a SQL query without using prepared statements, parameterized queries, or proper escaping
-
Check input sanitizationSearch the application code for sanitization functions applied to the Password parameter before database operations. Look for functions like mysqli_real_escape_string, htmlspecialchars, or parameterized query implementationsAffected if No input sanitization or validation is performed on the Password parameter before it is used in SQL queries
-
Confirm database interactionReview how the login form handles authentication. Examine if the Password field value is passed directly to a database query to verify credentialsAffected if The login form uses the Password parameter directly in an SQL query to authenticate users without proper safeguards
-
Test for SQL injection susceptibilityIf authorized, submit a single quote (') or SQL metacharacters in the Password field and observe if SQL errors are returned or if the application behavior changes unexpectedlyAffected if Submitting special characters in the Password field triggers database errors or alters authentication logic, confirming the injection point exists
You are affected if your environment hosts the /index2.php login form and the Password parameter is used in unsanitized SQL queries for authentication.
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 with parameterized queries/prepared statements for the Password field and all user inputs in index2.php; implement input validation and apply principle of least privilege to database accounts.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11471 — 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-2026-11471 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