VulnerabilityPublished 26 Mar 2026

CVE-2026-4835: code-projects Accounting System · Cross-site Scripting

Affects code-projects Accounting SystemSource CVE Database V5

Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 26 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-projectsAccounting System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-4835, organizations should implement strict input validation and output encoding on the costumer_name parameter to neutralize malicious scripts. Employing context-aware encoding (e.g., HTML entity encoding) before rendering user input in the web interface is critical. Web application firewalls (WAFs) can be configured to detect and block common XSS payloads targeting this endpoint. Until an official patch is released, consider disabling or restricting access to the vulnerable add_costumer.php functionality if feasible. Conduct security code reviews to identify similar vulnerabilities in other parts of the application. Educate users about the risks of clicking suspicious links and encourage the use of modern browsers with built-in XSS protections. Monitoring web server logs for unusual input patterns targeting this parameter can help detect exploitation attempts early. Finally, maintain a robust incident response plan to quickly address any successful attacks.

Description

A security vulnerability has been detected in code-projects Accounting System 1.0. Impacted is an unknown function of the file /my_account/add_costumer.php of the component Web Application Interface. Such manipulation of the argument costumer_name leads to cross site scripting. The attack may be performed from remote. The exploit has been disclosed publicly and may be used.

Impact

The primary impact of this XSS vulnerability is the potential compromise of user session integrity and confidentiality. Attackers could execute arbitrary scripts in the context of authenticated users, leading to theft of session cookies, credentials, or sensitive data displayed in the application. This can facilitate further attacks such as account takeover or phishing. While availability is not directly affected, the trustworthiness of the accounting system could be undermined, impacting business operations and user confidence. Organizations relying on this software may face regulatory and compliance risks if sensitive financial data is exposed. The medium severity rating reflects the moderate risk due to the need for user interaction and the limited scope of the affected component. However, the ease of remote exploitation without authentication makes it a notable threat for organizations with exposed web interfaces.

Summary

CVE-2026-4835 is a cross-site scripting (XSS) vulnerability identified in version 1.0 of the code-projects Accounting System, specifically within the web application interface component located at /my_account/add_costumer.php. The vulnerability arises from improper sanitization or encoding of the costumer_name parameter, allowing an attacker to inject malicious JavaScript code. This flaw can be exploited remotely without requiring authentication, although user interaction is necessary for the payload to execute, such as a victim clicking a crafted link or submitting manipulated input. The vulnerability impacts the integrity and confidentiality of user sessions by potentially enabling session hijacking, defacement, or redirection to malicious sites. The CVSS 4.0 vector indicates low attack complexity and no privileges required, but user interaction is needed. Despite the absence of known active exploits, the public disclosure of the vulnerability increases the likelihood of exploitation attempts. The vulnerability does not affect availability and is limited to version 1.0 of the product. No official patches have been linked yet, so mitigation relies on input validation, output encoding, and possibly web application firewall rules.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 02:46 UTC

Technical details

References

Community reviews

Related threats