CVE-2026-0580VulnerabilityPublished 5 Jan 2026Updated 23 Feb 2026

CVE-2026-0580: SourceCodester API Key Manager App · Cross Site Scripting

Affects SourceCodester API Key Manager AppSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% 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 5 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
SourceCodesterAPI Key Manager App	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-0580, organizations should implement strict input validation and output encoding in the Import Key Handler component to prevent injection of malicious scripts. Employing a robust Content Security Policy (CSP) can help limit the impact of any injected scripts. Restrict access to the Import Key Handler functionality to trusted users and networks, minimizing exposure. Conduct thorough code reviews and security testing focusing on input handling in the affected application version. Monitor application logs and user activity for signs of suspicious behavior indicative of exploitation attempts. If possible, isolate the API Key Manager App from public-facing interfaces or place it behind additional authentication and web application firewalls (WAFs) that can detect and block XSS payloads. Stay alert for vendor patches or updates addressing this vulnerability and apply them promptly once available. Educate users about phishing risks to reduce the likelihood of successful social engineering attacks that could trigger exploitation.

Description

A vulnerability was found in SourceCodester API Key Manager App 1.0. Affected by this vulnerability is an unknown functionality of the component Import Key Handler. Performing a manipulation results in cross site scripting. The attack can be initiated remotely.

Impact

The primary impact of CVE-2026-0580 is the potential for attackers to execute arbitrary scripts in the context of users interacting with the vulnerable Import Key Handler component. This can lead to session hijacking, theft of authentication tokens, unauthorized actions performed on behalf of users, and potential pivoting to other parts of the application or network. Organizations using the SourceCodester API Key Manager App risk compromise of API keys and associated services, which could cascade into broader security breaches. Since the vulnerability requires user interaction, phishing or social engineering campaigns could be used to exploit it. The medium CVSS score reflects moderate risk; while it does not directly expose sensitive data or cause service outages, the integrity and trustworthiness of the application are undermined. If exploited in environments managing critical API keys, the consequences could be significant, including unauthorized access to backend systems and data exfiltration. The absence of known exploits reduces immediate risk but also means organizations must proactively address the vulnerability before attackers develop weaponized code.

Summary

CVE-2026-0580 is a cross-site scripting (XSS) vulnerability identified in the SourceCodester API Key Manager App version 1.0, specifically within an unspecified functionality of the Import Key Handler component. XSS vulnerabilities occur when an application does not properly sanitize user-supplied input, allowing attackers to inject malicious scripts that execute in the context of the victim's browser. In this case, the vulnerability can be triggered remotely without authentication, although it requires some level of user interaction (e.g., clicking a crafted link or submitting malicious input). The CVSS 4.0 vector indicates the attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:L), and user interaction needed (UI:P). The impact is limited to integrity (VI:L) with no direct impact on confidentiality or availability. This suggests that the attacker can manipulate data or perform unauthorized actions within the application context but cannot directly exfiltrate sensitive data or cause denial of service. The vulnerability resides in the Import Key Handler, which likely processes API key imports, a critical function for managing access credentials. Exploiting this flaw could allow attackers to execute arbitrary JavaScript in the victim’s browser, potentially leading to session hijacking, credential theft, or further exploitation of the application. No patches or known exploits are currently available, indicating the vulnerability is newly disclosed. The lack of CWE identifiers suggests incomplete classification, but the nature of the flaw aligns with CWE-79 (Improper Neutralization of Input During Web Page Generation).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 23:13 UTC

Technical details

References

Community reviews

Related threats