CVE-2026-4474
Received Received - Intake
Cross-Site Scripting in itsourcecode University Management System Admin Module

Publication date: 2026-03-20

Last updated on: 2026-04-29

Assigner: VulDB

Description
A flaw has been found in itsourcecode University Management System 1.0. Impacted is an unknown function of the file /admin_single_student_update.php. This manipulation of the argument st_name causes cross site scripting. The attack may be initiated remotely. The exploit has been published and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-20
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-03-20
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
angeljudesuarez university_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': "CVE-2026-4474 is a Cross-Site Scripting (XSS) vulnerability found in version 1.0 of the University Management System, specifically in the file /admin_single_student_update.php. The vulnerability occurs because the st_name parameter is not properly encoded or filtered, allowing attackers to inject malicious JavaScript code that executes in the victim's browser."}, {'type': 'paragraph', 'content': 'This means that an attacker can manipulate the st_name argument to run arbitrary scripts on the web page, potentially affecting any user who views the page with the injected code.'}] [1]


How can this vulnerability impact me? :

The impact of this vulnerability is significant and includes the following risks:

  • Attackers can steal sensitive information such as cookies and session tokens.
  • Perform unauthorized actions on behalf of the victim.
  • Deface web pages or redirect users to malicious sites.
  • Potentially gain control over the victim’s browser.

Exploitation does not require authentication or login, making it easier for attackers to exploit remotely.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': "This vulnerability can be detected by testing the affected URL parameter for Cross-Site Scripting (XSS) by injecting a proof-of-concept payload. Specifically, the `st_name` parameter in the URL `/admin_single_student_update.php` can be tested by injecting `<script>alert('XSS')</script>` and observing if the script executes in the browser."}, {'type': 'paragraph', 'content': 'A simple detection method is to use curl or a browser to send a request like:'}, {'type': 'list_item', 'content': 'curl "http://127.0.0.1/ums/admin_single_student_update.php?st_name=<script>alert(\'XSS\')</script>"'}, {'type': 'paragraph', 'content': 'If the alert box appears or the script is reflected unencoded in the response, the vulnerability is present.'}] [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Properly encode user inputs when rendering them in HTML or JavaScript contexts to prevent execution of injected scripts.
  • Implement strict input validation and filtering on the `st_name` parameter to allow only expected formats and reject or escape script tags and event handlers.
  • Deploy a Content Security Policy (CSP) to restrict sources of executable scripts and prevent unauthorized inline or external script execution.
  • Set secure cookie flags such as `HttpOnly` and `Secure` to protect sensitive cookies from theft via JavaScript.
  • Conduct regular security audits and code reviews to detect and fix XSS and other vulnerabilities promptly.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart