dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-65136

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
In manikandan580 School-management-system 1.0, a reflected XSS vulnerability exists in /studentms/admin/contact-us.php via the pagedes 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 confidence

A reflected cross-site scripting (XSS) vulnerability exists in the School Management System 1.0 admin panel at /studentms/admin/contact-us.php. The pagedes POST parameter is not properly sanitized before being reflected back in the HTTP response, allowing an attacker to inject malicious JavaScript that executes in the context of the victim's browser.

MitigationImplement strict input validation and output encoding for the pagedes parameter. Use context-appropriate encoding (HTML entity encoding for HTML context) such as htmlspecialchars() with ENT_QUOTES before reflecting any user input.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if School Management System is installed
    Look for the application web root directory containing 'studentms' folder, or check web server document root for /studentms path
    Affected if The School Management System 1.0 application is present on the server
  2. Verify the vulnerable file exists
    Check if the file /studentms/admin/contact-us.php exists in the web root
    Affected if The contact-us.php file exists in the admin directory
  3. Confirm admin panel accessibility
    Attempt to access the admin login page at /studentms/admin/ or check if admin routes are reachable from the network
    Affected if The admin panel is accessible (even with valid credentials, the vulnerability requires admin access)
  4. Test pagedes parameter for reflected input
    Send a POST request to /studentms/admin/contact-us.php with a benign test payload in the pagedes parameter (e.g., <script>alert(1)</script>), then examine the HTTP response to see if the payload is reflected unescaped
    Affected if The pagedes parameter reflects the submitted value in the response without HTML encoding (no &lt; or &gt; entities)
  5. Verify the application version
    Check application version file, footer in admin panel, or any version indicator within the studentms installation
    Affected if The installed version is 1.0 or falls within the affected version range

You are affected if School Management System 1.0 is installed with the /studentms/admin/contact-us.php file accessible and the pagedes POST parameter reflects input without HTML entity encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and output encoding for the pagedes parameter. Use context-appropriate encoding (HTML entity encoding for HTML context) such as htmlspecialchars() with ENT_QUOTES before reflecting any user input.

Recommended fix Moderate confidence
  1. Locate the file /studentms/admin/contact-us.php in the project.
  2. Find the code that handles the pagedes POST parameter (e.g., $pagedes = $_POST['pagedes'];).
  3. Before reflecting the value in the HTML, sanitize it using htmlspecialchars with appropriate flags, for example: $pagedes = htmlspecialchars($pagedes, ENT_QUOTES, 'UTF-8');
  4. Ensure the sanitized variable is used in the output instead of the raw POST value.
  5. Test the fix by submitting a crafted pagedes payload (e.g., <script>alert(1)</script>) and verify it is properly escaped.
  6. Commit the changes to the repository.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65136 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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