CVE-2020-11825: CSRF
First published: Thu Apr 16 2020(Updated: )
In Dolibarr 10.0.6, forms are protected with a CSRF token against CSRF attacks. The problem is any CSRF token in any user's session can be used in another user's session. CSRF tokens should not be valid in this situation.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Dolibarr Dolibarr Erp\/crm | =10.0.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this Dolibarr issue?
The vulnerability ID for this Dolibarr issue is CVE-2020-11825.
What is the severity rating of CVE-2020-11825?
The severity rating of CVE-2020-11825 is 8.8 (high).
How does Dolibarr 10.0.6 protect against CSRF attacks?
Dolibarr 10.0.6 protects against CSRF attacks by using Cross-Site Request Forgery (CSRF) tokens.
What is the problem with CSRF token validation in Dolibarr 10.0.6?
The problem is that any CSRF token in any user's session can be used in another user's session.
How can I fix the CSRF token vulnerability in Dolibarr 10.0.6?
To fix the CSRF token vulnerability in Dolibarr 10.0.6, it is recommended to update to a version that addresses this issue.
- collector/nvd-index
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/type
- agent/weakness
- vendor/dolibarr
- canonical/dolibarr dolibarr erp\/crm
- version/dolibarr dolibarr erp\/crm/10.0.6