dbcve.org
Umbraco FormsApplication · Umbraco

CVE-2025-68924

HIGH · 7.5 CVSS v3.1 Published 2026-01-16
Fix available
A fix is available. Upgrade to after 8.13.16 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
In Umbraco UmbracoForms through 8.13.16, an authenticated attacker can supply a malicious WSDL (aka Webservice) URL as a data source for remote code execution.

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

UmbracoForms through 8.13.16 allows authenticated users to configure data sources with arbitrary WSDL URLs, enabling the application to fetch and process malicious external WSDL definitions that can lead to remote code execution on the server.

MitigationUpgrade to UmbracoForms version 8.13.17 or later. As an interim control, restrict access to the data source configuration interface to trusted administrators only and consider network segmentation to limit outbound requests from the application server.

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
Umbraco FormsApplication
Affected:<= 8.13.16

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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 Umbraco Forms version installed
    In the Umbraco backoffice, navigate to the Help menu (question mark icon) or check the Packages section to view the installed version of Umbraco Forms. Alternatively, check the ~/bin/Umbraco.Forms.Core.dll file version properties or the packages.config file in the solution.
    Affected if The installed version is 8.13.16 or lower.
  2. Verify data source configuration access
    In the Umbraco backoffice, go to the Forms section and check if a user role (other than Administrators) has access to the Data Sources settings. Navigate to Forms > Settings > Data Sources and examine which user groups can access this configuration area.
    Affected if Non-administrator users or roles have permission to create or edit data sources.
  3. Inspect existing data source configurations
    In the Umbraco backoffice, navigate to Forms > Settings > Data Sources and review all configured data sources. Check each entry for the WSDL URL field to identify any URLs pointing to external or untrusted locations.
    Affected if Any data source is configured with a WSDL URL pointing to an external or untrusted server.
  4. Check for anonymous or all-users access to Forms settings
    Review the Umbraco user group permissions in the Users section. Specifically examine whether the Forms Creator, Editor, or other non-admin groups have been granted access to the Data Sources configuration area.
    Affected if A broad or default user group (such as All Users or sensitive groups) has access to configure data sources.

Your environment is affected if Umbraco Forms version 8.13.16 or lower is installed AND non-administrator users have access to configure data sources with WSDL URLs.

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 a release after 8.13.16
Interim mitigation

Upgrade to UmbracoForms version 8.13.17 or later. As an interim control, restrict access to the data source configuration interface to trusted administrators only and consider network segmentation to limit outbound requests from the application server.

Recommended fix Moderate confidence

Umbraco Forms 8.13.17

  1. Backup the Umbraco website and database.
  2. Update the Umbraco Forms NuGet package to version 8.13.17 (or the latest stable release).
  3. Clear any cached files and rebuild the solution.
  4. Test the application to ensure forms work correctly and that remote data sources (WSDL) are properly validated or disabled.
  5. Consult the release notes for any additional configuration changes or security settings.
Caveat Review release notes for any breaking changes; minimal expected risk

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

Fix this in Umbraco Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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