Dolibarr 21.0.0 before 24.0.0 contains an authorization bypass vulnerability caused by an inverted boolean condition in the private-project membership check within the clonetasks mass action handler in htdocs/core/actions_massactions.inc.php. Authenticated users with project creation permission but without access to a target private project can exploit the flawed !in_array() check to clone tasks into unauthorized private projects.
CVE-2026-77923
Score 4.3 from GitHub Security Advisory published 2026-08-24. the CNA's CVSS baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 29, 2026
Advisory Details (3)
Auto-updated Aug 24, 2026Dolibarr 21.0.0 < 24.0.0 Authorization Bypass via clonetasks Mass Action | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dolibarr-authorization-bypass-via-clonetasks-mass-actioncommit 1730aa56675b (Dolibarr/dolibarr)
Patch available: Dolibarr/dolibarr 24.0.0 (contains commit 1730aa56675b)
https://github.com/Dolibarr/dolibarr/commit/1730aa56675b31cfede895fdae55b673d887fb8f24.0.0
Patch available: Dolibarr/dolibarr 24.0.0
https://github.com/Dolibarr/dolibarr/releases/tag/24.0.0Vendor Advisories for CVE-2026-77923(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 12:00 UTCEG score recompute
- 2026-08-29 11:59 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:08 UTCGHSA enrichment
- 2026-08-27 22:07 UTCEG score recompute
- 2026-08-27 22:07 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 21:33 UTCEG score recompute
- 2026-08-26 21:33 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 20:59 UTCEG score recompute
- 2026-08-25 20:59 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 20:25 UTCEG score recompute
- 2026-08-24 20:11 UTCEG score recompute
- 2026-08-24 19:36 UTCEG score recompute
- 2026-08-24 19:36 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-77923?
When was CVE-2026-77923 disclosed?
Is CVE-2026-77923 actively exploited?
What is the CVSS score of CVE-2026-77923?
How do I remediate CVE-2026-77923?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77923
Is Your Infrastructure Affected by CVE-2026-77923?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.