CVE-2019-17223
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 · uneditedThere is HTML Injection in the Note field in Dolibarr ERP/CRM 10.0.2 via user/note.php.
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 confidenceHTML Injection vulnerability in Dolibarr ERP/CRM 10.0.2 where the Note field in user/note.php does not properly sanitize user input before rendering. Unsanitized HTML can be stored and executed when other users view the note, potentially leading to stored XSS attacks.
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= 10.0.2CVSS 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.
-
Identify Dolibarr installation versionCheck the version.php file in the Dolibarr root directory or look at the footer of the Dolibarr web interface for the version numberAffected if The installed version is exactly 10.0.2 (other versions may have different behavior)
-
Locate the vulnerable note.php fileNavigate to the user/note.php file in the Dolibarr installation directory and confirm it existsAffected if The file user/note.php exists in the installation (this is where the vulnerable code resides)
-
Check if user notes feature is accessibleLog in as a user with access to user profiles and navigate to a user card to access the Notes section, or directly access user/note.phpAffected if The Note field functionality is enabled and accessible to the current user role
-
Inspect note rendering for sanitizationCreate a test note with HTML content (e.g., <script>alert(1)</script> or <img src=x onerror=alert(1)>), save it, and view the note as a different user to see if the HTML executesAffected if The HTML/JavaScript input renders and executes in the browser when viewing the note (indicating no output encoding)
-
Verify database storage of raw HTMLCheck the database table (typically llx_user_note or similar) where notes are stored - look for raw HTML tags in the stored contentAffected if The note content is stored in the database with unescaped HTML tags
A user is affected if they are running Dolibarr version 10.0.2, have access to the Note field in user/note.php, and can create/view notes that execute unescaped HTML/JavaScript when rendered.
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 output encoding on the Note field in user/note.php. Sanitize HTML tags from user input using a allowlist approach or properly escape HTML entities when displaying the note content.
- 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-2019-17223 — 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-17223 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