VulnerabilityPublished 23 Mar 2026

CVE-2026-4575: code-projects Exam Form Submission · Cross-site Scripting

Affects code-projects Exam Form SubmissionSource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projectsExam Form Submission	Affected =1.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:code-projects:exam_form_submission:*:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-4575, organizations should implement strict input validation and output encoding for the 'sname' parameter in the /admin/update_s2.php endpoint. Specifically, applying context-aware encoding (e.g., HTML entity encoding) before rendering user input can prevent script injection. Until an official patch is released, administrators should consider restricting access to the vulnerable administrative interface via network segmentation or VPN to reduce exposure. Employing Content Security Policy (CSP) headers can help limit the impact of injected scripts by restricting script sources. Additionally, educating administrators about phishing and social engineering risks can reduce the likelihood of user interaction exploitation. Monitoring web server logs for suspicious requests targeting the 'sname' parameter and anomalous administrator behavior can aid in early detection. Finally, organizations should track vendor updates and apply patches promptly once available.

Description

A flaw has been found in code-projects Exam Form Submission 1.0. This issue affects some unknown processing of the file /admin/update_s2.php. This manipulation of the argument sname causes cross site scripting. The attack can be initiated remotely. The exploit has been published and may be used.

Impact

The primary impact of CVE-2026-4575 is the potential for attackers to execute arbitrary scripts in the context of an authenticated administrator's browser session. This can lead to session hijacking, unauthorized actions performed on behalf of the administrator, or defacement of the administrative interface. While confidentiality and availability are not directly affected, the integrity of administrative operations can be compromised. Organizations using the affected software may face risks of unauthorized data manipulation or exposure of sensitive administrative functions. The requirement for high privileges and user interaction limits the scope of exploitation but does not eliminate risk, especially in environments where administrators may be targeted via phishing or social engineering. The lack of known active exploitation reduces immediate threat but does not preclude future attacks, especially given that a public exploit is available. This vulnerability could undermine trust in the affected application and disrupt administrative workflows if exploited.

Summary

CVE-2026-4575 is a cross-site scripting vulnerability identified in the code-projects Exam Form Submission software, specifically version 1.0. The vulnerability arises from improper handling of the 'sname' parameter in the /admin/update_s2.php endpoint. This parameter is susceptible to injection of malicious JavaScript code because the application fails to adequately sanitize or encode user input before rendering it in the web interface. The attack vector is remote and does not require authentication bypass, but it does require the attacker to have high privileges (PR:H) and user interaction (UI:P), such as tricking an administrator into clicking a crafted link or submitting a malicious form. The CVSS 4.0 vector indicates no impact on confidentiality or availability, but a low impact on integrity, as the attacker can execute scripts in the context of the victim's browser session. This could lead to session hijacking, defacement, or redirection to malicious sites. Although an exploit has been published, there are no known widespread attacks exploiting this vulnerability in the wild. The vulnerability is limited to version 1.0 of the Exam Form Submission product, and no patches have been officially released yet. The vulnerability is classified as medium severity with a CVSS score of 4.8, reflecting the moderate risk posed by the requirement for high privileges and user interaction.

References

Community reviews

Loading reviews…