CVE-2022-30875
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 · uneditedDolibarr 12.0.5 is vulnerable to Cross Site Scripting (XSS) via Sql Error Page.
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 confidenceDolibarr 12.0.5 contains a reflected Cross Site Scripting (XSS) vulnerability in its SQL error page. User-supplied input is rendered without proper sanitization or output encoding when the application displays SQL errors, 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= 12.0.5CVSS 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 Dolibarr installationLocate the Dolibarr installation directory and identify the version file or admin page that displays the software version. This is typically found in the main Dolibarr directory or through the About/Help section in the web interface.Affected if The system is running Dolibarr and the installed version is exactly 12.0.5
-
Verify exact version numberCompare the installed Dolibarr version to the affected range. This specific CVE affects only version 12.0.5. Check the version string in the Dolibarr configuration or admin panel.Affected if The installed version is precisely 12.0.5 (not 12.0.4, 12.0.6, or other versions)
-
Identify SQL error page accessibilityTrigger a SQL error condition by submitting malformed query parameters or intentionally invalid input to Dolibarr endpoints, then observe if the application displays raw SQL error messages.Affected if The application displays SQL error pages with user-supplied input reflected back without sanitization
You are affected only if your Dolibarr installation is exactly version 12.0.5 and your system displays SQL error pages with unescaped user input.
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 · scopedApply vendor-supplied patch for this CVE. Until then, implement output encoding on all error page output and consider Web Application Firewall rules to detect and block XSS payloads in query parameters.
Dolibarr 12.0.6 or later (preferably latest stable 17.x/18.x)
- 1. Backup your current Dolibarr installation and database before any upgrade
- 2. Download the latest stable version of Dolibarr from the official website (dolibarr.org) or GitHub repository
- 3. Review the Dolibarr upgrade documentation for your specific version migration path
- 4. Install the new version following the standard upgrade procedures
- 5. Verify the SQL error page now properly escapes output to prevent XSS
- 6. Test that the application functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30875 — 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-2022-30875 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