dbcve.org
Dolibarr Erp\/crmApplication · Dolibarr

CVE-2024-31503

HIGH · 7.5 CVSS v3.1 Published 2024-04-17
Fix available
A fix is available. Upgrade to 19.0.1 or later.
See remediation →
79/100
Remediation priority · High
Remotely reachable

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 · unedited
Incorrect access control in Dolibarr ERP CRM versions 19.0.0 and before, allows authenticated attackers to steal victim users' session cookies and CSRF protection tokens via user interaction with a crafted web page, leading to account takeover.

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 confidence

Dolibarr ERP CRM versions 19.0.0 and before contains an incorrect access control vulnerability allowing authenticated attackers to steal victim users' session cookies and CSRF protection tokens through user interaction with a crafted webpage, leading to session hijacking and full account takeover.

MitigationUpgrade to a Dolibarr version after 19.0.0 that addresses this access control flaw; alternatively, implement additional security controls including secure cookie flags (HttpOnly, Secure, SameSite), CSRF token regeneration on authentication, and consider implementing SameSite cookie policies to mitigate cookie theft via crafted web pages.

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
Dolibarr Erp\/crmApplication
Affected:< 19.0.1

CVSS 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
High
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Dolibarr installation version
    Locate the version file (typically version.php in the root directory or conf.php) or access the Dolibarr admin panel About page to read the installed version number
    Affected if The installed version is 19.0.0 or earlier (any version below 19.0.1)
  2. Confirm authentication is possible
    Verify that user authentication is enabled and the system accepts user logins (check if the /dolibarr/htdocs/index.php or login page is accessible and functional)
    Affected if The system allows user authentication, enabling authenticated attackers to access the application
  3. Check session cookie security flags
    Inspect session cookies set by the application using browser developer tools (F12 > Application/Storage tab) or by examining the PHP session configuration; look for HttpOnly, Secure, and SameSite attributes
    Affected if Session cookies lack HttpOnly or Secure flags, making them accessible to client-side scripts and vulnerable to theft via crafted webpages
  4. Verify CSRF token handling
    Examine how CSRF tokens are generated and handled in the application; check if tokens are regenerated upon authentication or remain static across sessions
    Affected if CSRF tokens are not regenerated on login or are exposed in a manner that allows stealing via crafted webpages

You are affected if running Dolibarr version 19.0.0 or earlier and your system allows authenticated user access, especially if session cookies lack security flags or CSRF tokens are vulnerable to theft.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 19.0.1 or later
Fixed in 19.0.1
Interim mitigation

Upgrade to a Dolibarr version after 19.0.0 that addresses this access control flaw; alternatively, implement additional security controls including secure cookie flags (HttpOnly, Secure, SameSite), CSRF token regeneration on authentication, and consider implementing SameSite cookie policies to mitigate cookie theft via crafted web pages.

Recommended fix Moderate confidence

19.0.1

  1. 1. Back up your current Dolibarr installation and database before upgrading.
  2. 2. Download Dolibarr version 19.0.1 from the official Dolibarr website or GitHub repository.
  3. 3. Follow the standard Dolibarr upgrade procedure: extract the new version files, update the 'htdocs' and 'dolibarr' directories, and run any database migration scripts if required.
  4. 4. Verify the upgrade was successful by logging in and checking the Dolibarr version in the admin panel.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dolibarr Erp\/crm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31503 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-31503 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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