CVE-2019-6965
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 · uneditedAn XSS issue was discovered in i-doit Open 1.12 via the src/tools/php/qr/qr.php url parameter.
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 confidenceCross-site scripting (XSS) vulnerability in i-doit Open 1.12 allows remote attackers to inject arbitrary JavaScript via the 'url' parameter in src/tools/php/qr/qr.php. The application fails to properly sanitize or validate user-supplied input before including it in the generated output, enabling script execution in the context of the victim's browser.
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.12CVSS 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.0/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.
-
Verify i-doit versionCheck the installed version of i-doit by accessing the application admin panel, version information file, or using the command: cat /path/to/i-doit/version.php (or similar version file in the installation directory)Affected if The installed version is exactly 1.12 (i-doit Open 1.12)
-
Confirm vulnerable file existsCheck if the file src/tools/php/qr/qr.php exists in the web root directory. Use: ls -la /path/to/webroot/src/tools/php/qr/qr.phpAffected if The file qr.php exists in the src/tools/php/qr/ directory of the i-doit installation
-
Verify web application is accessibleConfirm the i-doit web application is accessible over HTTP/HTTPS. Test by accessing the main URL: http(s)://your-domain/src/tools/php/qr/qr.phpAffected if The application is reachable and the vulnerable endpoint is exposed to the network
-
Test url parameter for XSSSend a request to src/tools/php/qr/qr.php with a test payload in the url parameter, such as: http(s)://your-domain/src/tools/php/qr/qr.php?url=<script>alert('XSS')</script>Affected if The application reflects the unsanitized url parameter value in the response, causing script execution in the browser
A user is affected if they are running i-doit Open version 1.12 and the web application is accessible with the vulnerable qr.php endpoint handling the url parameter without sanitization.
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 proper input validation and output encoding for the 'url' parameter in the qr.php file. Apply context-aware escaping (HTML entity encoding) for any user input rendered in the response.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6965 — 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-2019-6965 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