Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-0342 Overview
CVE-2025-0342 is a stored cross-site scripting (XSS) vulnerability in CampCodes Computer Laboratory Management System 1.0. The flaw resides in the /class/edit/edit endpoint, where the s_lname parameter is not properly sanitized before being rendered in the application. Attackers can inject arbitrary JavaScript that executes in the browser of any user viewing the affected page. The exploit has been publicly disclosed, and other parameters in the same endpoint may be affected. The weakness is tracked as CWE-79.
Critical Impact
Authenticated attackers can inject persistent JavaScript payloads via the s_lname parameter, enabling session theft, credential harvesting, and arbitrary actions in the context of other users.
Affected Products
- CampCodes Computer Laboratory Management System 1.0
- CPE: cpe:2.3:a:campcodes:computer_laboratory_management_system:1.0:*:*:*:*:*:*:*
- Component path: /class/edit/edit (parameter s_lname)
Discovery Timeline
- 2025-01-09 - CVE-2025-0342 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-0342
Vulnerability Analysis
The vulnerability is a stored XSS flaw in the edit workflow of CampCodes Computer Laboratory Management System 1.0. The application accepts the s_lname parameter through the /class/edit/edit endpoint and persists its value without encoding or filtering. When the stored value is later rendered in a response, the browser interprets any embedded HTML or JavaScript as executable content. A low-privileged authenticated user can plant a payload that fires every time another user, including an administrator, loads the affected view.
Because the payload executes within the trusted origin of the application, attackers can read session cookies, perform background requests on behalf of victims, and pivot to privileged functionality. The vendor advisory from VulDB confirms the issue is remotely exploitable over the network with low attack complexity. According to the public references, other parameters handled by the same endpoint may also lack output encoding.
Root Cause
The root cause is missing input validation and output encoding on user-supplied data written to and later read from server-side storage. The application trusts the s_lname field end-to-end, violating the contextual-escaping requirements defined by CWE-79.
Attack Vector
Exploitation requires network access and a low-privileged account on the target instance. An attacker submits a crafted request to /class/edit/edit containing a JavaScript payload in s_lname. The payload is stored and executed in the browser of any subsequent user who views the record. A proof of concept is published at the GitHub PoC for Stored XSS.
No verified exploitation code is reproduced here. Refer to the public PoC and the VulDB CVE-290829 Details entry for payload specifics.
Detection Methods for CVE-2025-0342
Indicators of Compromise
- HTTP POST or PUT requests to /class/edit/edit containing <script>, onerror=, onload=, or javascript: substrings in the s_lname parameter.
- Stored database values in laboratory management records containing HTML tags or event handlers in last-name fields.
- Unexpected outbound requests from browsers of authenticated users loading list or detail views that render student records.
- Session cookies appearing in web server referer logs or external telemetry, suggesting exfiltration via injected script.
Detection Strategies
- Deploy web application firewall (WAF) rules that inspect form parameters for XSS payload patterns on the /class/edit/ path.
- Review application logs for POST requests to /class/edit/edit originating from low-privileged accounts with anomalous payload sizes.
- Perform periodic database queries against name and label columns to identify records containing HTML or JavaScript syntax.
Monitoring Recommendations
- Alert on repeated access to the /class/edit/edit endpoint from the same session within short time windows.
- Monitor browser Content Security Policy (CSP) violation reports if CSP is enforced on the application.
- Correlate administrative session activity with subsequent anomalous API calls that may indicate script-driven abuse.
How to Mitigate CVE-2025-0342
Immediate Actions Required
- Restrict access to the Computer Laboratory Management System to trusted networks or place it behind an authenticated reverse proxy until a fix is available.
- Audit existing records for stored HTML or JavaScript in s_lname and related fields, and purge any malicious content.
- Revoke and rotate active session tokens for administrative users to invalidate any payloads that may already have captured credentials.
- Enable a strict Content Security Policy that blocks inline scripts to reduce the impact of stored payloads.
Patch Information
At the time of publication, no vendor patch is listed in the referenced advisories. Consult the CampCodes Security Blog and the VulDB #290829 entry for update notices. Organizations running CampCodes Computer Laboratory Management System 1.0 should treat the application as unpatched and apply compensating controls.
Workarounds
- Implement a WAF signature that blocks HTML tags and JavaScript event handlers submitted to /class/edit/edit.
- Apply server-side input validation at a reverse proxy layer to reject non-alphanumeric characters in name parameters such as s_lname.
- Enforce HTTPOnly and SameSite attributes on session cookies to limit theft via injected script.
- Remove or disable the edit workflow for untrusted user roles until output encoding is implemented upstream.
# Example ModSecurity rule to block script payloads in s_lname
SecRule ARGS:s_lname "@rx (?i)(<script|onerror=|onload=|javascript:)" \
"id:1002025,phase:2,deny,status:403,log,\
msg:'CVE-2025-0342 XSS attempt in s_lname parameter'"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

