DotnetnukeApplication · Dnnsoftware

CVE-2025-52485

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-21
Fix available
A fix is available. Upgrade to 10.0.1 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
DNN (formerly DotNetNuke) is an open-source web content management platform (CMS) in the Microsoft ecosystem. In versions 6.0.0 to before 10.0.1, DNN.PLATFORM allows a specially crafted request to inject scripts in the Activity Feed Attachments endpoint which will then render in the feed. This issue has been patched in version 10.0.1.

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

DNN (DotNetNuke) versions 6.0.0 through 10.0.0 contain a stored Cross-Site Scripting (XSS) vulnerability in the Activity Feed Attachments endpoint. Attackers can inject malicious scripts that persist in the feed and execute when other users view the affected content.

MitigationUpgrade DNN.PLATFORM to version 10.0.1 or later to patch the XSS vulnerability in the Activity Feed Attachments endpoint.

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
DotnetnukeApplication
Affected:>= 6.0.0, < 10.0.1

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. Determine installed DNN version
    Log in as Host or Admin, navigate to Host > About, or locate the VersionInfo.config or web.config file in the website root to read the installed DNN version number
    Affected if The installed version falls within 6.0.0 through 10.0.0 (inclusive)
  2. Verify Activity Feed module presence
    Access the DNN site as Host or Admin and check if the Activity Feed module exists on the site by navigating to Pages or checking the module list in the Control Panel
    Affected if The Activity Feed module is installed and present on the DNN instance
  3. Confirm Activity Feed Attachments feature is in use
    Locate the Activity Feed module on a site page (commonly on the profile or home page) and determine if the Attachments feature is enabled or configurable within the module settings
    Affected if The Activity Feed module has Attachments functionality enabled and accessible to users
  4. Inspect Activity Feed Attachments configuration
    Access the Activity Feed module settings as an administrator and examine the configuration for file upload or attachment handling in the module parameters
    Affected if The Activity Feed Attachments endpoint is exposed and accepts user-supplied content

The environment is affected if DNN version is between 6.0.0 and 10.0.0 and the Activity Feed module with Attachments feature is enabled on the site.

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

Upgrade DNN.PLATFORM to version 10.0.1 or later to patch the XSS vulnerability in the Activity Feed Attachments endpoint.

Recommended fix Moderate confidence

DNN Platform 10.0.1

  1. 1. Back up your current DNN installation and database before any upgrade
  2. 2. Download DNN Platform version 10.0.1 from the official DNN download source (dotnetnuke.com)
  3. 3. Follow the official DNN upgrade documentation to apply version 10.0.1
  4. 4. After upgrade, verify the Activity Feed Attachments endpoint no longer accepts script injection
  5. 5. Test that existing Activity Feed functionality works correctly post-upgrade

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

Fix this in Dotnetnuke Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-52485 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