Skip to main content
Menu
CVEs

ERP CRM code injection in document upload file conversion

CVE-2026-133327Published November 19, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

Dolibarr ERP CRM has a code injection flaw in its Document Upload feature, where file conversion handling lets an attacker inject code. An attacker can reach it remotely over the network, but must first log in with a low-privilege account.

Written by a model

Original description

A vulnerability was identified in Dolibarr ERP CRM up to 23.0.4. This affects the function dol_convert_file in the library htdocs/core/lib/files.lib.php of the component Document Upload. Such manipulation leads to code injection. The attack can be launched remotely. The exploit is publicly available and might be used. Upgrading to version 24.0.0 is able to mitigate this issue. The name of the patch is 9b6368b2a9eae3eec690b2ce22c4f291f0051540. Upgrading the affected component is advised.

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133327 (Dolibarr ERP CRM Document Upload files.lib.php dol_convert_file code injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133327 (entry last updated 2026-11-19):
Affected:
- Dolibarr ERP CRM: versions 23.0.0, 23.0.1, 23.0.2, 23.0.3, 23.0.4
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133327 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133327 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Dolibarr/dolibarr/pull/38020
- https://github.com/Dolibarr/dolibarr/commit/9b6368b2a9eae3eec690b2ce22c4f291f0051540
- https://github.com/Dolibarr/dolibarr/releases/tag/24.0.0
- https://vuldb.com/vuln/440553
- https://vuldb.com/vuln/440553/cti
- https://vuldb.com/cve/CVE-2026-133327
- https://vuldb.com/submit/1045443
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133327
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133327"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 10

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133327
RecordNVD · CVE-2026-133327
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
Exploithelx.io · en/blog/advisory-dolibarr
Other links 7
AdvisoryVulDB · Advisory #440553
AdvisoryVulDB · Threat intelligence #440553
AdvisoryVulDB · CVE-2026-133327 record
AdvisoryVulDB · Submission #1045443
PatchGitHub · Dolibarr/dolibarr · Pull request #38020
PatchGitHub · Dolibarr/dolibarr · Commit 9b6368b2
PatchGitHub · Dolibarr/dolibarr · Release 24.0.0

Questions about CVE-2026-133327

Is CVE-2026-133327 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133327?

ERP CRM: versions 23.0.0, 23.0.1, 23.0.2, 23.0.3, 23.0.4.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.