dbcve.org
AutomationApplication · Nintex

CVE-2025-27924

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-10
Fix available
A fix is available. Upgrade to 5.8 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Nintex Automation 5.6 and 5.7 before 5.8 has a stored XSS issue associated with the "Navigate to a URL" action.

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

Nintex Automation versions 5.6 and 5.7 before 5.8 contain a stored cross-site scripting (XSS) vulnerability in the 'Navigate to a URL' action. Attackers can inject malicious JavaScript into the URL parameter, which is then stored and executed when other users interact with the affected workflow action.

MitigationUpgrade Nintex Automation to version 5.8 or later. Additionally, implement output encoding and input validation for URL parameters in workflow actions to prevent XSS exploitation.

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
AutomationApplication
Affected:>= 5.6, < 5.8

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Nintex Automation version
    Access the Nintex Automation admin console or About page to determine the exact version number installed in your environment
    Affected if The installed version is 5.6, 5.7, or any version >= 5.6 but < 5.8
  2. Identify workflows using the 'Navigate to a URL' action
    Search your workflow repository or use the Nintex workflow discovery feature to locate all workflows that contain the 'Navigate to a URL' action
    Affected if Any workflows exist that use this action, making them potential carriers of the stored XSS payload
  3. Inspect URL parameter values in affected workflows
    Open each workflow containing the 'Navigate to a URL' action and examine the configured URL parameter for any unexpected or malicious-looking characters, script tags, or encoded payloads
    Affected if The URL parameter contains unsanitized user-supplied input or appears to contain script injection attempts
  4. Review workflow execution history for suspicious activity
    Check workflow audit logs and execution history for entries involving the 'Navigate to a URL' action that show unusual URL patterns or repeated executions
    Affected if Historical executions show URLs containing JavaScript handlers or unusual patterns consistent with XSS payloads
  5. Check for unexpected content in workflow definitions
    Export or examine the raw workflow definition files (XML or JSON format depending on your Nintex version) and search for script tags or javascript: URIs within URL parameter fields
    Affected if Workflow definitions contain encoded or plain-text script injections in URL fields

You are affected if your Nintex Automation version is 5.6 or 5.7 (or any version >= 5.6 but < 5.8) and you have workflows using the 'Navigate to a URL' action with untrusted URL parameters.

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 5.8 or later
Fixed in 5.8
Interim mitigation

Upgrade Nintex Automation to version 5.8 or later. Additionally, implement output encoding and input validation for URL parameters in workflow actions to prevent XSS exploitation.

Recommended fix High confidence

Nintex Automation 5.8

  1. Back up the Nintex Automation installation and database before proceeding
  2. Review the Nintex Automation 5.8 release notes for any changes or migration requirements
  3. Download Nintex Automation version 5.8 from the official Nintex download portal
  4. Apply the upgrade following the standard Nintex upgrade documentation for your deployment type
  5. After upgrading, verify that the stored XSS vulnerability in the 'Navigate to a URL' action has been resolved by testing the action with appropriate input validation
Caveat Review 5.8 release notes for any configuration or compatibility changes that may affect your workflows

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

Fix this in Automation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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