CVE-2025-34317
BaseFortify
Publication date: 2025-10-28
Last updated on: 2025-11-03
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ipfire | ipfire | to 2.29 (inc) |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
| ipfire | ipfire | 2.29 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a stored cross-site scripting (XSS) issue in IPFire versions prior to 2.29 (Core Update 198). An authenticated attacker can inject arbitrary JavaScript code through the TLS_HOSTNAME parameter when adding a new DNS entry. The injected script is stored and later executed in the web interface when other users view the affected DNS configuration, because the application does not properly sanitize or encode the TLS_HOSTNAME parameter.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute arbitrary JavaScript code in the context of other users who view the DNS configuration. This can lead to session hijacking, unauthorized actions performed on behalf of users, or theft of sensitive information accessible through the web interface.