dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-24320

HIGH · 8.0 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 15.1.10.6 / 16.1.5.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. This vulnerability is due to an incomplete fix for CVE-2024-31156 https://my.f5.com/manage/s/article/K000138636 .  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stored cross-site scripting (XSS) vulnerability exists in an undisclosed page of the BIG-IP Configuration utility that allows an authenticated attacker to execute arbitrary JavaScript in the context of the currently logged-in user. This vulnerability stems from an incomplete fix for CVE-2024-31156, indicating the original remediation was not comprehensive.

MitigationApply the complete patch from F5 that fully addresses CVE-2024-31156 and its incomplete fix. Until then, limit access to the Configuration utility to trusted users only and monitor for anomalous JavaScript behavior.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Big Ip Access Policy ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6>= 16.1.0, < 16.1.5.2>= 17.1.0, < 17.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6>= 16.1.0, < 16.1.5.2>= 17.1.0, < 17.1.2
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, < 15.1.10.6>= 16.1.0, < 16.1.5.2>= 17.1.0, < 17.1.2
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10.6>= 16.1.0, < 16.1.5.2>= 17.1.0, < 17.1.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6>= 16.1.0, < 16.1.5.2>= 17.1.0, < 17.1.2
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6>= 16.1.0, < 16.1.5.2>= 17.1.0, < 17.1.2
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, < 15.1.10.6>= 16.1.0, < 16.1.5.2>= 17.1.0, < 17.1.2
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, < 15.1.10.6>= 16.1.0, < 16.1.5.2>= 17.1.0, < 17.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check BIG-IP version
    Run `tmsh show /sys version` or inspect /etc/default/smallRelease.version to obtain the installed BIG-IP version
    Affected if The version falls within 15.1.0 to <15.1.10.6, 16.1.0 to <16.1.5.2, or 17.1.0 to <17.1.2
  2. Verify Configuration utility is enabled
    Run `tmsh list /sys httpd` to confirm the Configuration utility web service (httpd) is running and enabled
    Affected if The Configuration utility is accessible and running on the system
  3. Identify installed BIG-IP modules
    Run `tmsh list /sys module` to list which F5 modules (APM, AFM, AWM, ASM, AVR, etc.) are installed on the system
    Affected if Any of the affected modules (APM, AFM, AWM, ASM, Analytics, AAM, AVR, Automation Toolchain) are installed in the affected version range
  4. Check Configuration utility access controls
    Review the access profile and user role assignments for the Configuration utility via `tmsh list /auth user` and check for any untrusted accounts with administrative or editor access
    Affected if Untrusted or low-privilege users have access to the Configuration utility interface where the XSS could be triggered

The environment is affected if BIG-IP is running a version within the ranges 15.1.0 to <15.1.10.6, 16.1.0 to <16.1.5.2, or 17.1.0 to <17.1.2 AND the Configuration utility is accessible to users who could inject malicious JavaScript.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.1.10.6 / 16.1.5.2 / 17.1.2 or later
Fixed in 15.1.10.616.1.5.217.1.2
Interim mitigation

Apply the complete patch from F5 that fully addresses CVE-2024-31156 and its incomplete fix. Until then, limit access to the Configuration utility to trusted users only and monitor for anomalous JavaScript behavior.

Recommended fix High confidence

15.1.10.6+ (15.1.x), 16.1.5.2+ (16.1.x), or 17.1.2+ (17.1.x)

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI login page.
  2. 2. Create a full configuration backup using 'tmsh save sys config' and download the UCS archive from /var/local/ucs/
  3. 3. Schedule a maintenance window as upgrades require downtime.
  4. 4. For version 15.1.x: Upgrade to version 15.1.10.6 or later.
  5. 5. For version 16.1.x: Upgrade to version 16.1.5.2 or later.
  6. 6. For version 17.1.x: Upgrade to version 17.1.2 or later.
  7. 7. Follow F5 upgrade documentation for your specific deployment (single or cluster setup).
  8. 8. After upgrade, verify the version is no longer vulnerable by checking 'tmsh show sys version'.
Caveat F5 upgrades may require careful planning for high-availability clusters and may have specific prerequisites; review F5 upgrade guides before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24320 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data