CVE-2025-8372
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 code-projects Exam Form Submission 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /admin/update_s7.php. The manipulation of the argument credits leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may 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 Exam Form Submission 1.0 allows remote attackers to inject malicious SQL queries via the 'credits' parameter in /admin/update_s7.php. The lack of parameterized queries or input sanitization enables attackers to manipulate database queries.
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 Exam Form Submission installationLocate the web application files on your server. Search for directories or files containing 'exam' or 'form' in the name, typically within the web root directory.Affected if The Code Projects Exam Form Submission application is installed on the server.
-
Verify the vulnerable file existsCheck if the file /admin/update_s7.php exists within the application directory. This is the specific file containing the SQL injection vulnerability.Affected if The file /admin/update_s7.php is present in the application installation.
-
Check application versionLocate version information for the Exam Form Submission application. Check for a version file, README, or metadata within the application root directory.Affected if The installed version is Exam Form Submission 1.0.
-
Identify admin endpoint accessibilityDetermine if the /admin/update_s7.php endpoint is exposed to network access. Check web server configuration and firewall rules for access to the /admin/ path.Affected if The /admin/update_s7.php endpoint is accessible from the network (not restricted to localhost or authenticated users only).
-
Inspect parameter processingReview the update_s7.php file code, specifically looking for how the 'credits' parameter is handled in database queries. Look for direct string concatenation without parameterized queries.Affected if The 'credits' parameter is processed via direct SQL query construction without prepared statements or input sanitization.
The environment is affected if Exam Form Submission version 1.0 is installed, the /admin/update_s7.php file exists, and the credits parameter is processed without parameterized queries.
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 in update_s7.php, apply proper input validation on the credits parameter, and restrict database user privileges to minimum necessary.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8372 — 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-8372 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