Security readout for executives and security teams
Plain-English summary
Dolibarr 6.0.2 has an XSS issue in product details. If exposed in a business system, malicious JavaScript could run in another user’s browser when product information is viewed. The sources do not provide CVSS, CWE, affected-version range beyond 6.0.2, or confirmed exploitation.
Executive priority
Treat this as a targeted remediation item for Dolibarr 6.0.2 systems, not an emergency based on current evidence. Prioritize if the system is internet-facing, multi-user, or used by privileged business staff.
Technical view
CVE-2017-1000509 describes a cross-site scripting vulnerability in Dolibarr 6.0.2 product details that can result in JavaScript execution. The provided sources identify a GitHub issue as confirmation but do not include scoring, root-cause details, exploit maturity, or a named fixed release.
Likely exposure
Exposure is most likely in Dolibarr 6.0.2 deployments using product records, especially where product-detail content can be edited by less-trusted users or viewed by privileged staff. The source bundle does not establish exposure for other versions.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Practical impact depends on who can modify product details and who views them. XSS can support session abuse, data exposure, or unauthorized actions within the victim’s browser context.
Researcher notes
Evidence is limited to the CVE description and Dolibarr GitHub issue reference. Do not assume broader affected versions, a specific fixed release, or active exploitation without vendor or authoritative confirmation.
Mitigation direction
- Inventory Dolibarr deployments and flag version 6.0.2 for review.
- Review the linked Dolibarr issue and vendor release notes for fixed-version guidance.
- Upgrade or patch according to Dolibarr-supported guidance where available.
- Restrict product creation and editing to trusted users until remediated.
- Review product-detail content for unexpected script-like or unsafe HTML content.
Validation and detection
- Confirm deployed Dolibarr version and whether product management is enabled.
- Identify users or integrations allowed to create or edit product details.
- Review product-detail fields for unsafe HTML or script-like content.
- Use safe non-executing XSS checks in staging to verify output encoding.
- Check audit logs for unexpected product-detail changes before remediation.
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-2017-1000509 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/7727CVE reference · x_refsource_CONFIRM
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.