VulnerabilityPublished 31 Jan 2024Updated 29 May 2025

CVE-2024-1111: SourceCodester QR Code Login System · Cross-site Scripting

Affects SourceCodester QR Code Login SystemSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

4.3Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Jan 2024
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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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
SourceCodester QR Code Login System	Affected =1.0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should first assess whether they are using SourceCodester QR Code Login System version 1.0. If so, immediate steps should include implementing strict input validation and output encoding on the 'qr-code' parameter within add-user.php to neutralize malicious scripts. Employing Content Security Policy (CSP) headers can further reduce the risk by restricting the execution of unauthorized scripts. Organizations should also conduct security awareness training to educate users about the risks of clicking unknown links or interacting with suspicious QR codes. Monitoring web application logs for unusual input patterns targeting the 'qr-code' parameter can help detect exploitation attempts. Additionally, employing web application firewalls (WAFs) with rules to detect and block XSS payloads targeting this parameter can provide a compensating control until a patch is released.

Description

A vulnerability, which was classified as problematic, has been found in SourceCodester QR Code Login System 1.0. Affected by this issue is some unknown functionality of the file add-user.php. The manipulation of the argument qr-code leads to cross site scripting. The attack may be launched remotely. VDB-252470 is the identifier assigned to this vulnerability.

Impact

For European organizations using SourceCodester QR Code Login System 1.0, this vulnerability poses a risk of client-side script injection that can compromise user sessions and trust. While the direct impact on backend systems is limited, the exploitation of this XSS flaw can lead to phishing attacks, credential theft, or unauthorized actions performed on behalf of legitimate users. This can result in reputational damage, loss of customer trust, and potential regulatory scrutiny under GDPR if personal data is compromised through session hijacking or data exfiltration. Organizations relying on this system for authentication should be aware that attackers can remotely exploit this vulnerability without needing credentials, increasing the risk profile. However, since the vulnerability requires user interaction, the risk can be somewhat mitigated by user awareness and security controls. The lack of known exploits in the wild suggests limited immediate threat but does not preclude future exploitation attempts.

Summary

CVE-2024-1111 is a cross-site scripting (XSS) vulnerability identified in version 1.0 of the SourceCodester QR Code Login System, specifically within the add-user.php file. The vulnerability arises from improper sanitization or validation of the 'qr-code' parameter, which can be manipulated by an attacker to inject malicious scripts. This vulnerability is classified under CWE-79, indicating that it is a reflected or stored XSS issue. The attack vector is remote and does not require authentication, but it does require user interaction, such as a victim clicking a crafted link or visiting a malicious webpage that triggers the vulnerable parameter. The CVSS 3.1 base score is 4.3, indicating a medium severity level. The impact primarily affects the integrity of the system, as the attacker can execute scripts in the context of the victim's browser, potentially leading to session hijacking, defacement, or redirection to malicious sites. Confidentiality and availability impacts are not directly affected by this vulnerability. No known exploits are currently reported in the wild, and no patches have been published yet. The vulnerability affects only version 1.0 of the product, which is a specialized QR code login system likely used in web applications for authentication purposes.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
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.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 01:28 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats