dbcve.org
FirewareOperating system · Watchguard

CVE-2025-1545

HIGH · 7.5 CVSS v3.1 Published 2025-12-04
Fix available
A fix is available. Upgrade to 12.5.14 / 12.11.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
An XPath Injection vulnerability in WatchGuard Fireware OS may allow a remote unauthenticated attacker to retrieve sensitive information from the Firebox configuration through an exposed authentication or management web interface. This vulnerability only affects Firebox systems that have at least one authentication hotspot configured.

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 · high confidence

An XPath Injection vulnerability in WatchGuard Fireware OS allows remote unauthenticated attackers to retrieve sensitive information from Firebox configuration through the web interface. Attackers can manipulate XPath queries via input fields in the authentication hotspot to extract data from XML configuration files.

MitigationDisable authentication hotspot if not required, or apply vendor patches when available. Restrict access to the management web interface to trusted networks only.

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
FirewareOperating system
Affected:>= 2025.1, < 2025.1.3>= 11.11, < 12.11.5>= 11.11, < 12.5.14

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Confirm authentication hotspot is enabled
    Log into the WatchGuard Firebox web management interface and navigate to Dashboard > Hotspot or Authentication > Hotspot settings. Verify whether the authentication hotspot feature is turned on.
    Affected if Authentication hotspot is enabled and accessible to unauthenticated users
  2. Check Fireware OS version
    In the Firebox management web UI, go to Dashboard or System > About to view the installed Fireware OS version number.
    Affected if Version is 2025.1 through 2025.1.2, or 11.11 through 12.11.4, or 11.11 through 12.5.13
  3. Verify web interface is exposed
    Check network firewall rules to determine if TCP ports 80 or 443 (or custom HTTPS ports) for the Firebox management interface are open to untrusted networks or the internet.
    Affected if Management web interface is accessible from untrusted networks

You are affected if the authentication hotspot feature is enabled AND your Fireware OS version falls within 2025.1-2025.1.2, 11.11-12.11.4, or 11.11-12.5.13, and the management interface is reachable by attackers.

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 12.5.14 / 12.11.5 / 2025.1.3 or later
Fixed in 12.5.1412.11.52025.1.3
Interim mitigation

Disable authentication hotspot if not required, or apply vendor patches when available. Restrict access to the management web interface to trusted networks only.

Recommended fix High confidence

2025.1.3 (for 2025.1.x), 12.11.5 (for 12.11.x), 12.5.14 (for 12.5.x), or latest supported version if on 11.x

  1. 1. Identify the currently installed Fireware OS version by logging into the Firebox management interface or checking the device status.
  2. 2. Determine which upgrade path applies based on current version: for 2025.1.x line, upgrade to 2025.1.3 or later; for 12.5.x line, upgrade to 12.5.14 or later; for 12.11.x line, upgrade to 12.11.5 or later; for 11.12.x line, upgrade to a supported version as 11.x is end-of-life.
  3. 3. Download the appropriate firmware upgrade from the WatchGuard support portal at www.watchguard.com/support/firmware/.
  4. 4. Back up the current Firebox configuration before performing the upgrade.
  5. 5. Upload and apply the firmware upgrade through the Firebox management interface (Policy Manager, Web UI, or WatchGuard Cloud), or via the CLI using the 'firmware' command.
  6. 6. Verify the upgrade was successful and the device is functioning normally.
  7. 7. Confirm the XPath injection vulnerability is remediated by ensuring the authentication hotspot feature is no longer exposed or is functioning with patched code.
Caveat Review WatchGuard release notes for any compatibility changes or configuration adjustments required when upgrading between major versions; older 11.x versions may have limited upgrade paths

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

Fix this in Fireware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1545 — 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-1545 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