Stored XSS via unsanitized time synchronization value
Published Oct 28, 2025 · Updated Oct 28, 2025
Stored XSS in IPFire before 2.29 (Core Update 198) allows remote authenticated users to execute JavaScript in other users' browsers. The /cgi-bin/time.cgi handler stores UPDATE_VALUE from default time-synchronization updates and renders it without HTML sanitization or output encoding. An authenticated user must change that setting, and the script runs when another user views the affected Time Server configuration page.
Summary
What happened
Stored XSS in IPFire before 2.29 (Core Update 198) allows remote authenticated users to execute JavaScript in other users' browsers. The /cgi-bin/time.cgi handler stores UPDATE_VALUE from default time-synchronization updates and renders it without HTML sanitization or output encoding. An authenticated user must change that setting, and the script runs when another user views the affected Time Server configuration page.
The record
- CVE
- CVE-2025-34308
- Published
- Oct 28, 2025
- Updated
- Oct 28, 2025
- Vendor
- IPFire Project
- Product
- IPFire
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 28, 2025CVE publishedPublication date reported by the CVE source.
- Oct 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.29 (Core Update 198)
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- IPFire Bug 13883 researcher proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo