CVE-2025-65134
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 · uneditedIn manikandan580 School-management-system 1.0, a reflected cross-site scripting (XSS) vulnerability exists in /studentms/admin/contact-us.php via the email POST parameter.
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 reflected cross-site scripting (XSS) vulnerability exists in the contact-us.php file of the School-management-system 1.0 application. The vulnerability is triggered through the email POST parameter, allowing an attacker to inject malicious JavaScript code that executes in the victim's browser when the form is submitted.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 if School-management-system is installedSearch for the contact-us.php file in your web root directories (common paths: /contact-us.php, /php/contact-us.php, or /includes/contact-us.php). Also check for files containing 'School Management System' in headers or footers.Affected if The contact-us.php file from School-management-system version 1.0 exists on the server.
-
Verify the application versionCheck for a version file (version.php), README, or admin dashboard that displays the software version. Compare against version 1.0.Affected if The installed version is School-management-system 1.0.
-
Inspect the contact-us.php source code for email handlingOpen contact-us.php and search for the code handling the 'email' POST parameter (look for $_POST['email'] or similar). Check if the email value is reflected in the HTML response without sanitization functions like htmlspecialchars() or filter_var().Affected if The email parameter is directly echoed or printed back in the response without encoding or sanitization.
-
Check if the contact form is accessible and functionalAccess the contact-us.php page via HTTP GET request. Confirm the form accepts POST requests to the same endpoint and processes the email field.Affected if The contact form is live and processes user input through the email POST parameter.
You are affected if School-management-system version 1.0 is installed, the contact-us.php file exists, and the email parameter is reflected without proper HTML encoding or sanitization in the source code.
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 proper input validation and output encoding for the email parameter. Use PHP htmlspecialchars() or a sanitization library to escape user input before reflecting it back in the response.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65134 — 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-65134 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