How severe is CVE-2007-2637?

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

Which packages are affected by CVE-2007-2637?

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

How do I fix CVE-2007-2637?

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

How do I detect CVE-2007-2637 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-2637 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.

How does O3 Security protect against CVE-2007-2637?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2007-2637 can be triaged on real exposure rather than presence alone.

Is CVE-2007-2637 actively exploited in the wild?

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

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

CVE-2007-2637 was published on May 13, 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-2637 — moin

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

MoinMoin Improper ACL handling for calendars and includes

Also known asGHSA-cmg7-xr2j-4r9vPYSEC-2026-675

Published

May 13, 2007

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

MoinMoin before 20070507 does not properly enforce ACLs for calendars and includes, which allows remote attackers to read certain pages via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Debian:10	`moin`	all versions	1.5.7-2

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.7-2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-2637 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2007-2637 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2007-2637. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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-458-1Ubuntu

Frequently Asked Questions

MoinMoin before 20070507 does not properly enforce ACLs for calendars and includes, which allows remote attackers to read certain pages via unspecified vectors.

O3 Security · Impact-Aware SCA

Is CVE-2007-2637 in your dependencies?

O3 Security finds CVE-2007-2637 across Debian:10 dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works