How severe is CVE-2010-0717?

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

Which packages are affected by CVE-2010-0717?

CVE-2010-0717 affects the following packages: moin (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2010-0717?

Update moin to 1.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-0717 is resolved across your whole dependency graph.

How do I detect CVE-2010-0717 in my PyPI dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2010-0717 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-0717 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2010-0717?

CVE-2010-0717 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 81th 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-2010-0717?

CVE-2010-0717 is classified as CWE-16 (CWE-16). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2010-0717 published, and has it been updated?

CVE-2010-0717 was published on May 2, 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.

🐍 PyPI

Not in CISA KEV

CVE-2010-0717 — moin

CVE-2010-0717 is a CWE-16 vulnerability in moin. A fix is available for moin — see the affected versions and patch details below.

MoinMoin has improper default configuration

Also known asPYSEC-2010-3

Published

May 2, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk-0.02%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍moin

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

Description

The default configuration of cfg.packagepages_actions_excluded in MoinMoin before 1.8.7 does not prevent unsafe package actions, which has unspecified impact and attack vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`moin`	all versions	1.8.7`pip install --upgrade 'moin==1.8.7'`

Affected Products

1 product · 44 configurations

Application

moinmoinmoinmo

≤ 1.8.6

24 versions

1.5.01.5.11.5.21.5.31.5.41.5.51.5.5a1.5.61.5.71.5.81.6.01.6.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update moin to 1.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-0717 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Ubuntu

USN-911-1Ubuntu

Frequently Asked Questions

The default configuration of `cfg.packagepages_actions_excluded` in MoinMoin before 1.8.7 does not prevent unsafe package actions, which has unspecified impact and attack vectors.

O3 Security · Impact-Aware SCA

Is CVE-2010-0717 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works