How severe is CVE-2010-0669?

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

Which packages are affected by CVE-2010-0669?

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

How do I fix CVE-2010-0669?

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

How do I detect CVE-2010-0669 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-0669 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-0669 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-0669 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-0669?

CVE-2010-0669 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 80th 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.

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

CVE-2010-0669 was published on May 2, 2022 and was last updated on December 6, 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-0669 — moin

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

MoinMoin improper sanitizes user profiles

Also known asPYSEC-2010-2

Published

May 2, 2022

Updated

Dec 6, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐍moin🐍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

MoinMoin before 1.8.7 and 1.9.x before 1.9.2 does not properly sanitize user profiles, which has unspecified impact and attack vectors.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`moin`	all versions	1.8.7`pip install --upgrade 'moin==1.8.7'`
🐍PyPI	`moin`	≥ 1.9&&< 1.9.2	1.9.2`pip install --upgrade 'moin==1.9.2'`

Affected Products

1 product · 46 configurations

Application

moinmoinmoinmo

≤ 1.8.6

26 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-0669 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.

Frequently Asked Questions

MoinMoin before 1.8.7 and 1.9.x before 1.9.2 does not properly sanitize user profiles, which has unspecified impact and attack vectors.

O3 Security · Impact-Aware SCA

Is CVE-2010-0669 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works