Security readout for executives and security teams
Plain-English summary
Dolibarr 6.0.4 has a cross-site scripting issue in a product statistics page. A user would need to click an attacker-crafted link, after which browser cookies could be exposed. The provided sources do not show CVSS scoring, CISA KEV listing, or active exploitation evidence.
Executive priority
Treat this as a targeted remediation item, not an emergency based on the supplied evidence. Prioritize if Dolibarr 6.0.4 is internet-accessible or handles privileged business sessions.
Technical view
CVE-2019-1010016 affects Dolibarr 6.0.4 in htdocs/product/stats/card.php. The reported impact is cookie stealing via XSS, with user interaction required through a crafted link. The source bundle provides no CWE, CVSS vector, fixed-version statement, or confirmed exploitation details.
Likely exposure
Exposure is limited to organizations running Dolibarr 6.0.4, especially where users can reach the affected product statistics route from browsers handling sensitive sessions.
Exploitation context
The cited CVE states the attack requires a victim to click a specially crafted link. KEV is false, and the provided sources do not substantiate active exploitation.
Researcher notes
Evidence is sparse: one CVE entry and a GitHub issue reference. Validate the affected code path and remediation from Dolibarr sources before assigning final severity or declaring fixed versions.
Mitigation direction
- Identify any Dolibarr 6.0.4 deployments and owners.
- Check Dolibarr vendor guidance and release notes for the appropriate fixed version.
- Upgrade or retire affected Dolibarr 6.0.4 instances when vendor-supported remediation is available.
- Restrict access to Dolibarr until remediation is complete.
- Invalidate sensitive sessions if exposure is suspected.
Validation and detection
- Confirm deployed Dolibarr versions across production and non-production systems.
- Check whether htdocs/product/stats/card.php exists on deployed instances.
- Review web logs for unusual access to the affected product stats route.
- Verify users cannot reach affected instances from untrusted networks.
- Confirm remediation against vendor guidance after any upgrade.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-1010016 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Dolibarr/dolibarr/issues/7962CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.