CVE-2025-59269: F5 BIG-IP · Cross-site Scripting
Affects F5 BIG-IPSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
F5f5/big-ippkg:rpm/f5/big-ipOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-59269, organizations should: 1) Monitor F5’s advisories closely and apply official patches or updates as soon as they become available for affected BIG-IP versions. 2) Restrict access to the BIG-IP Configuration utility to trusted networks and administrators only, using network segmentation and firewall rules to limit exposure. 3) Implement multi-factor authentication (MFA) for all administrative access to reduce the risk of credential compromise. 4) Conduct regular security awareness training to reduce the risk of social engineering attacks that could trigger user interaction exploitation. 5) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious input patterns targeting the management interface. 6) Audit and sanitize all user inputs in custom configurations or scripts interacting with BIG-IP to prevent injection of malicious code. 7) Regularly review administrative logs and session activities for unusual behavior indicative of attempted exploitation. 8) Consider deploying out-of-band management or jump servers to further isolate administrative access. These steps, combined with timely patching, will significantly reduce the risk posed by this vulnerability.
Description
A stored cross-site scripting (XSS) vulnerability exists in an undisclosed page of the BIG-IP Configuration utility that allows an attacker to run JavaScript in the context of the currently logged-in user. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.