How severe is CVE-2007-0857?

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

Which packages are affected by CVE-2007-0857?

CVE-2007-0857 affects the following packages: moin (Debian:10). Ecosystems affected: Debian:10.

How do I fix CVE-2007-0857?

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

How do I detect CVE-2007-0857 in my Debian:10 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-2007-0857 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-2007-0857 actively exploited in the wild?

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

CVE-2007-0857 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 84th 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-2007-0857 published, and has it been updated?

CVE-2007-0857 was published on February 8, 2007 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Withdrawn — this advisory has been retracted

📦 Debian:10

Not in CISA KEV

CVE-2007-0857 — moin

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

MoinMoin Multiple cross-site scripting (XSS) vulnerabilities

Also known asGHSA-m84w-vgwf-p893PYSEC-2026-678

Published

Feb 8, 2007

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% 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 Debian:10 packages — download data is not available via public APIs for these ecosystems.

Description

Multiple cross-site scripting (XSS) vulnerabilities in MoinMoin before 1.5.7 allow remote attackers to inject arbitrary web script or HTML via (1) the page info, or the page name in a (2) AttachFile, (3) RenamePage, or (4) LocalSiteMap action.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Debian:10	`moin`	all versions	1.5.3-1.2

Affected Products

1 product · 11 configurations

Application

moinmoinmoinmoin

≤ 1.5.6

10 versions

1.5.01.5.11.5.21.5.31.5.3_rc11.5.3_rc21.5.41.5.51.5.5_rc11.5.5a

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.5.3-1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-0857 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2007-0857 in your dependencies?

Find it across Debian:10, including transitive dependencies.

Scan my dependencies How O3 SCA works