CVE-2008-6540 json
DotNetNuke Default Machine Key Exposure
published 2009-03-30 17 y ago modified 2026-06-16 4 mo ago also GHSA-grw3-hjjm-5cjm , EUVD-2022-4007
- cvss
- 5.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 1
- Exploit-DB
Summary
DotNetNuke before 4.8.2, during installation or upgrade, does not warn the administrator when the default (1) ValidationKey and (2) DecryptionKey values cannot be modified in the web.config file, which allows remote attackers to bypass intended access restrictions by using the default keys.
Patch / fix
- nuget DotNetNuke.Core 4.8.2
Timeline
- First public exploit (EDB-31465)
- Published
Exploit prediction
2.48% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-31465 DotNetNuke 4.8.1 - Default 'ValidationKey' and 'DecriptionKey' Weak Encryption remote, 2008-03-21
- securityfocus.com http://www.securityfocus.com/bid/28391 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.1 | AV:N/AC:H/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | DotNetNuke.Core | <4.8.2 |
4.8.2 |
Classification
References
-
securityfocus.com
/bid/28391
vdb-entry, web, exploit
-
dotnetnuke.com
/News/SecurityBulletins/SecurityBulletinno12/tabid/1148/Default.aspx
web, vendor-advisory
-
secunia.com
/advisories/29488
third-party-advisory, web, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41399
vdb-entry, web
-
securityfocus.com
/archive/1/489957/100/0/threaded
mailing-list, web
-
osvdb.org
/43720
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2008-6540
advisory
-
github.com
/dnnsoftware/Dnn.Platform
package
Sources
- CVE List CVE-2008-6540
- GitHub Advisory GHSA-grw3-hjjm-5cjm
- NVD CVE-2008-6540
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.