CVE-2025-10596
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 Online Exam Form Submission 1.0. This affects an unknown part of the file /index.php. The manipulation of the argument usn results in sql injection. The attack can be launched 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 confidenceA SQL injection vulnerability exists in the usn parameter of /index.php in SourceCodester Online Exam Form Submission 1.0. Remote attackers can inject malicious SQL queries through the usn argument, potentially allowing unauthorized database access, data exfiltration, or complete system compromise. The CVSS 9.8 score indicates trivial exploitability with no authentication required.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm the application is installedLocate SourceCodester Online Exam Form Submission or Janobe Online Exam Form Submission in your web root directory. Check for the presence of index.php and related files.Affected if The application files exist in your environment.
-
Verify the application versionCheck your installed files for version markers such as a version.php file, a README file, or meta tags within PHP files that indicate version 1.0.Affected if The installed version is 1.0.
-
Locate the vulnerable endpointExamine the web server configuration or directly access /index.php?usn= to confirm the endpoint is accessible and the usn parameter is accepted.Affected if The /index.php file exists and accepts the usn parameter.
-
Inspect the SQL query handling for usn parameterOpen index.php in a code editor and search for SQL queries that incorporate the usn parameter without using prepared statements or parameter binding.Affected if The usn parameter is used directly in SQL queries without sanitization or prepared statements.
-
Check for input validation on usnReview the index.php code to determine if there is any input validation, sanitization, or type checking applied to the usn parameter before it is used in database operations.Affected if No input validation or sanitization exists for the usn parameter.
You are affected if you have SourceCodester/Janobe Online Exam Form Submission version 1.0 running and the usn parameter in /index.php is handled with dynamic SQL queries without prepared statements or input validation.
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 prepared statements/parameterized queries for the usn parameter and all user inputs. Apply input validation, enforce least privilege on database accounts, and conduct a full code audit for additional injection points.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10596 — 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-10596 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