CVE-2026-4595
Received Received - Intake
Cross-Site Scripting in Exam Form Submission /admin/update_s6.php

Publication date: 2026-03-23

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was determined in code-projects Exam Form Submission 1.0. This vulnerability affects unknown code of the file /admin/update_s6.php. Executing a manipulation of the argument sname can lead to cross site scripting. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-23
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-03-23
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
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': "The CVE-2026-4595 vulnerability is a Cross-Site Scripting (XSS) issue found in the Exam Form Submission Project V1.0, specifically in the '/admin/update_s6.php' file."}, {'type': 'paragraph', 'content': "The root cause is the improper handling of the 'sname' parameter, where user input is directly output to the web page without adequate encoding or filtering."}, {'type': 'paragraph', 'content': "This flaw allows attackers to inject malicious scripts, which execute in the victim's browser."}] [1]


How can this vulnerability impact me? :

[{'type': 'paragraph', 'content': 'Exploitation of this vulnerability can lead to the theft of cookies, session tokens, and other sensitive information.'}, {'type': 'paragraph', 'content': "Attackers can perform unauthorized actions on behalf of the victim, deface webpages, redirect users to malicious sites, and potentially gain full control over the victim's browser."}, {'type': 'paragraph', 'content': 'Notably, exploitation does not require user login or authorization, making it easier for attackers to launch remote attacks.'}] [1]


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': "The vulnerability is a Cross-Site Scripting (XSS) issue in the '/admin/update_s6.php' file, specifically involving the 'sname' parameter. Detection can involve testing this parameter by injecting typical XSS payloads such as <script>prompt(/xss/);</script> to see if the script executes."}, {'type': 'paragraph', 'content': 'You can use tools like curl or browser-based testing to send requests with malicious payloads to the vulnerable parameter and observe if the response reflects the injected script without proper encoding.'}, {'type': 'list_item', 'content': 'Example curl command to test the vulnerability: curl -G --data-urlencode "sname=<script>prompt(/xss/);</script>" https://targetsite.com/admin/update_s6.php'}, {'type': 'list_item', 'content': "Use web vulnerability scanners that support XSS detection to automate testing of the 'sname' parameter."}] [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include properly encoding all user inputs based on their context (HTML, JavaScript, CSS, URL) to prevent execution of injected scripts.

  • Implement strict input validation and filtering to accept only expected input formats and sanitize or reject malicious content such as script tags or event handlers.
  • Deploy a strict Content Security Policy (CSP) to restrict the sources from which scripts can be loaded and executed.
  • Set HttpOnly and Secure flags on sensitive cookies to prevent access via JavaScript and ensure cookies are transmitted only over HTTPS.
  • Conduct regular security audits and code reviews to detect and remediate 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