dbcve.org
DotnetnukeApplication · Dnnsoftware

CVE-2025-52487

HIGH · 7.5 CVSS v3.1 Published 2025-06-21
Fix available
A fix is available. Upgrade to 10.0.1 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
DNN (formerly DotNetNuke) is an open-source web content management platform (CMS) in the Microsoft ecosystem. In versions 7.0.0 to before 10.0.1, DNN.PLATFORM allows a specially crafted request or proxy to be created that could bypass the design of DNN Login IP Filters allowing login attempts from IP Addresses not in the allow list. 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 (formerly DotNetNuke) versions 7.0.0 through 10.0.0 contain an IP filter bypass vulnerability in the login mechanism. Attackers can use specially crafted requests or proxies to circumvent the configured Login IP Allow List, enabling unauthorized login attempts from IP addresses that should be blocked. This is an authentication bypass that undermines the intended IP-based access control.

MitigationUpgrade DNN.PLATFORM to version 10.0.1 or later, which contains the security patch for this vulnerability. Review and audit login logs for suspicious activity from non-allowed IP addresses.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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
    Access the DNN admin dashboard and navigate to Host > Host Settings, or check the version.dll/version.txt in the website root directory
    Affected if Version is 7.0.0 through 10.0.0 inclusive (versions below 10.0.1)
  2. Verify Login IP Allow List is configured
    In DNN admin panel, go to Security > Security Settings and locate the 'Login IP Allow List' or 'IP Filtering' section. Check if any IP addresses or ranges are defined in the allow list
    Affected if IP Allow List is populated with specific entries - the bypass only affects environments where IP filtering is meant to be enforced
  3. Review web.config for IP filtering configuration
    Examine the web.config file in the DNN root directory for <httpModules> or security-related IP filter settings, and check for any X-Forwarded-For or proxy header handling configurations
    Affected if IP filtering rules exist in configuration but the application relies on potentially spoofable IP detection methods
  4. Audit recent login attempts for IP anomalies
    Review DNN login logs (typically in Admin > Log Viewer or the EventLog table in the database) for login events where source IPs do not match the configured allow list
    Affected if Log entries show successful logins from IP addresses outside the defined allow list

Environment is affected if running DNN version 7.0.0 through 10.0.0 AND the Login IP Allow List feature is configured with restrictions that could be bypassed.

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, which contains the security patch for this vulnerability. Review and audit login logs for suspicious activity from non-allowed IP addresses.

Recommended fix High confidence

10.0.1

  1. Backup the existing DNN database and all website files
  2. Download DNN version 10.0.1 from the official DNN repository or distribution channel
  3. Test the upgrade in a non-production environment first
  4. Upload the 10.0.1 files to replace the existing installation, preserving the web.config and any custom configurations
  5. Run the upgrade installation process following standard DNN upgrade procedures
  6. Verify that the Login IP Filters are functioning correctly after upgrade
  7. Monitor the site for any issues and test user login functionality
Caveat Review DNN 10.0.1 release notes for any breaking changes or deprecations before upgrading

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

Fix this in Dotnetnuke Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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