CVE-2024-1111
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored cross-site scripting (XSS) vulnerability exists in SourceCodester QR Code Login System 1.0 within the add-user.php file. The qr-code parameter accepts unsanitized user input that is reflected back without proper output encoding, allowing execution of arbitrary JavaScript in the context of other users' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the installed product and versionIdentify the QR Code Login System application and verify the version number is 1.0. Check application documentation, headers, or the application itself for the version string.Affected if The system is running SourceCodester QR Code Login System version 1.0
-
Locate the add-user.php fileSearch the web root directory for the file add-user.php. Common paths may include /admin/, /php/, or the application root directory.Affected if The add-user.php file exists in the application directory
-
Inspect the qr-code parameter handling in add-user.phpOpen add-user.php and search for occurrences of 'qr-code' or $_POST/$_GET/$_REQUEST references that handle this parameter. Look for whether the input is being used directly in HTML output.Affected if The qr-code parameter is being processed and reflected in the page output without escaping functions (such as htmlspecialchars)
-
Verify lack of output encodingReview the code around the qr-code parameter usage to determine if any sanitization functions (htmlspecialchars, strip_tags, or similar) are applied before outputting the value to the browser.Affected if The qr-code value is output to the browser without htmlspecialchars or equivalent encoding
-
Test for stored XSS executionIf you have access to the application, submit a test payload in the qr-code field (such as <script>alert(1)</script>) and then access a page where this value is displayed to see if the script executes.Affected if The submitted JavaScript payload executes when the page containing the qr-code value is loaded
The system is affected if it runs SourceCodester QR Code Login System version 1.0 and the add-user.php file processes the qr-code parameter without output encoding.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement input validation and proper output encoding for the qr-code parameter in add-user.php. Use context-aware escaping functions and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1111 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1111 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data