dbcve.org
FirewareOperating system · Watchguard

CVE-2025-13938

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in WatchGuard Fireware OS (Autotask Technology Integration module) allows Stored XSS.

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

A Stored XSS vulnerability exists in the Autotask Technology Integration module of WatchGuard Fireware OS. The module fails to properly neutralize user-supplied input during web page generation, allowing attackers to inject malicious scripts that persist on the system and execute in the browsers of other users who access the compromised functionality.

MitigationUpdate Fireware OS to the latest version (12.11.5, 12.5.14, or 2025.1.3 or later) to remediate this vulnerability. As a compensating control, restrict access to the Autotask integration module to trusted users only until the patch is applied.

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>= 12.0.0, < 12.11.5>= 12.5, < 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check Fireware OS version
    Access the WatchGuard Firebox management web UI. Navigate to System > Status or the About page to view the installed Fireware OS version number.
    Affected if The installed version is >= 2025.1 and < 2025.1.3, OR >= 12.0.0 and < 12.11.5, OR >= 12.5 and < 12.5.14
  2. Confirm Autotask integration is enabled
    In the Firebox management UI, go to Subscriptions or Integration settings. Look for the Autotask Technology Integration module and determine if it is configured or active.
    Affected if The Autotask integration module is enabled or configured on the Firebox device
  3. Inspect Autotask configuration for injected content
    Access the Autotask integration configuration panel. Review all input fields including API credentials, endpoint URLs, and custom field parameters for unexpected characters or suspicious encoded content that could represent stored script tags.
    Affected if Malicious script content is found stored in any Autotask integration configuration fields

If the installed Fireware OS version falls within any of the affected version ranges AND the Autotask integration module is enabled, the environment is vulnerable to this Stored XSS flaw.

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

Update Fireware OS to the latest version (12.11.5, 12.5.14, or 2025.1.3 or later) to remediate this vulnerability. As a compensating control, restrict access to the Autotask integration module to trusted users only until the patch is applied.

Recommended fix High confidence

2025.1.3 (for 2025.1.x) | 12.5.14 (for 12.5.x) | 12.11.5 (for 12.0-12.11.x)

  1. 1. Identify the current Fireware OS version by accessing the Firebox management interface or using CLI command 'fwPrint'
  2. 2. Determine which version branch you are running (2025.1.x, 12.5.x, or 12.0-12.11.x)
  3. 3. For Fireware 2025.1.x branch: upgrade to version 2025.1.3
  4. 4. For Fireware 12.5.x branch: upgrade to version 12.5.14
  5. 5. For Fireware 12.0-12.11.x branch: upgrade to version 12.11.5
  6. 6. Download the appropriate firmware from the WatchGuard portal at www.watchguard.com
  7. 7. Upload and apply the firmware through the Firebox management interface (Policy Manager or Web UI)
  8. 8. After upgrade, verify the Autoktask Technology Integration module configuration
Caveat Review WatchGuard release notes for any configuration changes or compatibility considerations before upgrading

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-13938 — 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-13938 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