CVE-2022-41417: BlogEngine.NET v3.3.8.0 allows an attacker to create any folder with "files" prefix under ~/App_Data/.

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2022-41417 is a critical-severity flaw (CVSS 9.8) affecting blogengine.net. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

BlogEngine.NET v3.3.8.0 allows an attacker to create any folder with "files" prefix under ~/App_Data/.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.8% (top 44%)
CISA exploited list	No
Weakness	CWE-862
Published	2023-01-18
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: blogengine

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-01-18 14:15 UTCPublished CVE record published
2026-06-17 05:03 UTCUpdated Record last modified

blogengine blogengine.net DOWNGRADE

Affected: 3.3.8.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.3.8.0

1. Check installed version

apt-cache policy blogengine.net || rpm -q blogengine.net || blogengine.net --version

2. No fixed release: DOWNGRADE to a release before 3.3.8.0 (Debian / Ubuntu)

apt-cache madison blogengine.net sudo apt install blogengine.net=<VERSION_BEFORE_3.3.8.0> sudo apt-mark hold blogengine.net

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list blogengine.net sudo dnf downgrade blogengine.net-<VERSION_BEFORE_3.3.8.0> sudo dnf versionlock add blogengine.net

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-41417?

blogengine.net: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-41417 being exploited?

CVE-2022-41417 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-41417 affect?

CVE-2022-41417 affects blogengine.net. Severity is critical (CVSS 9.8). BlogEngine.NET v3.3.8.0 allows an attacker to create any folder with "files" prefix under ~/App_Data/.

How urgent is CVE-2022-41417?

Priority 53/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2023-33405 MEDIUM 6.1 UPGRADE Blogengine.net 3.3.8.0 and earlier is vulnerable to Open Redirect.
CVE-2023-33404 CRITICAL 9.8 UPGRADE An Unrestricted Upload vulnerability, due to insufficient validation on UploadControlled.cs file, in BlogEngin
CVE-2023-22858 MEDIUM 5.3 DOWNGRADE An Improper Access Control vulnerability in BlogEngine.NET 3.3.8.0, allows unauthenticated visitors to access
CVE-2023-22857 HIGH 8.5 DOWNGRADE A stored Cross-site Scripting (XSS) vulnerability in BlogEngine.NET 3.3.8.0, allows injection of arbitrary Jav
CVE-2023-22856 HIGH 8.5 DOWNGRADE A stored Cross-site Scripting (XSS) vulnerability in BlogEngine.NET 3.3.8.0, allows injection of arbitrary Jav

References

← Back to latest CVEs