CVE-2025-34300
Published: 16 July 2025
Summary
CVE-2025-34300 is a critical-severity Improper Input Validation (CWE-20) vulnerability. Its CVSS base score is 10.0 (Critical).
Operationally, ranked in the top 1.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
A template injection vulnerability exists in Sawtooth Software’s Lighthouse Studio versions prior to 9.16.14 via the ciwweb.pl Perl web application. The flaw, tracked as CVE-2025-34300 and assigned CWEs 20 and 1336, carries a CVSS 4.0 score of 10.0 reflecting network-exploitable arbitrary command execution with no authentication or user interaction required.
An unauthenticated attacker can supply malicious input to the affected web component and achieve full remote code execution, resulting in complete compromise of confidentiality, integrity, and availability on the target system as well as potential impact to the broader environment.
Vendor guidance directs users to upgrade to Lighthouse Studio 9.16.14 or later, as noted in the product version history. Public advisories from VulnCheck and Assetnote further detail the pre-authentication remote code execution path and recommend immediate patching for exposed instances.
The EPSS score rose sharply from a low baseline to a peak of 0.7782 on 2025-12-11 before receding to the current value of 0.7365, indicating that exploitation interest materialized after the July 2025 disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-21694
Vulnerability details
A template injection vulnerability exists in Sawtooth Software’s Lighthouse Studio versions prior to 9.16.14 via the ciwweb.pl http://ciwweb.pl/ Perl web application. Exploitation allows an unauthenticated attacker can execute arbitrary commands.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Directly implements checks on information inputs to reject invalid data before processing.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.