How severe is CVE-2013-4649?

No CVSS score has been assigned to CVE-2013-4649 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-4649?

CVE-2013-4649 affects the following packages: DotNetNuke.Core (NuGet), DotNetNuke.Core (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2013-4649?

Update DotNetNuke.Core to 6.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4649 is resolved across your whole dependency graph.

How do I detect CVE-2013-4649 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for DotNetNuke.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-4649 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2013-4649 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-4649, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-4649?

CVE-2013-4649 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-4649?

CVE-2013-4649 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2013-4649 published, and has it been updated?

CVE-2013-4649 was published on May 17, 2022 and was last updated on December 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

CVE-2013-4649 — DotNetNuke.Core

CVE-2013-4649 is a Cross-site Scripting (XSS) vulnerability in DotNetNuke.Core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for DotNetNuke.Core — see the affected versions and patch details below.

DotNetNuke (DNN) Cross-site scripting (XSS) vulnerability via the __dnnVariable parameter

Published

May 17, 2022

Updated

Dec 5, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

.NETDotNetNuke.Core.NETDotNetNuke.Core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Cross-site scripting (XSS) vulnerability in DotNetNuke (DNN) before 6.2.9 and 7.x before 7.1.1 allows remote attackers to inject arbitrary web script or HTML via the __dnnVariable parameter to the default URI.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`DotNetNuke.Core`	all versions	6.2.9`dotnet add package DotNetNuke.Core --version 6.2.9`
.NETNuGet	`DotNetNuke.Core`	≥ 7.0&&< 7.1.1	7.1.1`dotnet add package DotNetNuke.Core --version 7.1.1`

Affected Products

1 product · 65 configurations

Application

dotnetnukednnsoftware

≤ 6.2.8

64 versions

1.0.61.0.71.0.81.0.91.0.10d1.0.10e2.1.12.1.23.0.73.0.83.0.113.1.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Cross-site scripting (XSS) vulnerability in DotNetNuke (DNN) before 6.2.…

packetstormsecurity.comNVDAug 2017

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for DotNetNuke.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update DotNetNuke.Core to 6.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4649 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.