CVE-2024-33866
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 issue was discovered in linqi before 1.4.0.1 on Windows. There is /api/DocumentTemplate/{GUID] XSS.
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 · moderate confidenceA Cross-Site Scripting (XSS) vulnerability exists in the linqi document management system at the /api/DocumentTemplate/{GUID} endpoint in versions prior to 1.4.0.1 on Windows. The endpoint fails to properly sanitize or encode user-supplied input in the GUID parameter, allowing injection of malicious script.
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.4.0.1CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
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.
-
Identify the installed Linqi versionLocate the version information for the Linqi document management system - typically found in the application itself (About section), installation metadata, or configuration files within the Linqi installation directory on WindowsAffected if The installed version is anything prior to 1.4.0.1
-
Confirm the Windows platformVerify that the Linqi instance is running on a Windows operating system, as this vulnerability is specific to the Windows versionAffected if The system is running Linqi on Windows
-
Check endpoint accessibilityVerify that the /api/DocumentTemplate/{GUID} API endpoint is exposed and accessible within the environment - this could be internal network, VPN, or direct server access depending on deploymentAffected if The /api/DocumentTemplate endpoint is reachable and accepts requests
You are affected if your Linqi installation runs on Windows with a version earlier than 1.4.0.1 and the /api/DocumentTemplate endpoint is accessible
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.
dbcve · scoped1.4.0.1
Upgrade linqi to version 1.4.0.1 or later which contains the vendor patch. Alternatively, implement input validation and output encoding on the affected endpoint as a compensating control.
1.4.0.1
- 1. Verify current Linqi installation version by checking the application or configuration files
- 2. Download Linqi version 1.4.0.1 or later from the official source (linqi.help or www.linqi.de)
- 3. Create a full backup of the current Linqi installation including database and configuration files
- 4. Stop the Linqi service or application
- 5. Install version 1.4.0.1 following the official upgrade documentation
- 6. Start the Linqi service
- 7. Verify the XSS vulnerability in /api/DocumentTemplate/{GUID} endpoint is resolved by testing with a benign script payload
- 8. Monitor application logs for any errors post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33866 — 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-33866 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