Comodo Dome Firewall 2.7.0 Stored Cross-Site Scripting via license_activation
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Passive
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
Comodo Dome Firewall 2.7.0 contains a stored cross-site scripting vulnerability that allows attackers to inject malicious scripts by submitting crafted input to the newLicense parameter. Attackers can send POST requests to the license activation endpoint with script payloads in the newLicense field to execute arbitrary JavaScript in administrators' browsers.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2019-25405
- 2026-10-03 Alias added: GHSA-p6xr-26h9-q79c
References
More Comodo Dome Firewall vulnerabilities
- TI-2019-15475 Comodo Dome Firewall 2.7.0 Cross-Site Scripting via vpnfw CVSS 4.0MEDIUM 5.3
- TI-2019-15472 Comodo Dome Firewall 2.7.0 Stored Cross-Site Scripting via schedule CVSS 4.0MEDIUM 5.3
- TI-2019-15480 Comodo Dome Firewall 2.7.0 Reflected Cross-Site Scripting via antispyware CVSS 4.0MEDIUM 5.1
- TI-2019-15479 Comodo Dome Firewall 2.7.0 Cross-Site Scripting via dnsmasq CVSS 4.0MEDIUM 5.1
- TI-2019-15478 Comodo Dome Firewall 2.7.0 Reflected Cross-Site Scripting via smtpconfig CVSS 4.0MEDIUM 5.1
- TI-2019-15477 Comodo Dome Firewall 2.7.0 Reflected Cross-Site Scripting via https_exceptions CVSS 4.0MEDIUM 5.1
Sources
- CVE-2019-25405 · CVE Program
- CVE-2019-25405 · NVD
- FIRST EPSS
- GHSA-p6xr-26h9-q79c · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences