What is CVE-2007-2637?

CVE-2007-2637 is a medium-severity security vulnerability in moin (pip), affecting versions < 1.5.8. It is fixed in 1.5.8.

Which versions of moin are affected by CVE-2007-2637?

moin (pip) versions < 1.5.8 is affected.

Is there a fix for CVE-2007-2637?

Yes. CVE-2007-2637 is fixed in 1.5.8. Upgrade to this version or later.

Is CVE-2007-2637 exploitable, and should I be worried?

Whether CVE-2007-2637 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2007-2637 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2007-2637 in moin

Q: Which versions of moin are affected by CVE-2007-2637?

moin (pip) versions < 1.5.8 is affected.

Q: Is there a fix for CVE-2007-2637?

Yes. CVE-2007-2637 is fixed in 1.5.8. Upgrade to this version or later.

Q: Is CVE-2007-2637 exploitable, and should I be worried?

Whether CVE-2007-2637 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2007-2637 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2007-2637?

Upgrade moin to 1.5.8 or later.

Summary

MoinMoin Improper ACL handling for calendars and includes

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

Impact

Affected versions

moin (< 1.5.8)

Security releases

moin → 1.5.8 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade moin to 1.5.8 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2007-2637? CVE-2007-2637 is a medium-severity security vulnerability in moin (pip), affecting versions < 1.5.8. It is fixed in 1.5.8.
Which versions of moin are affected by CVE-2007-2637? moin (pip) versions < 1.5.8 is affected.
Is there a fix for CVE-2007-2637? Yes. CVE-2007-2637 is fixed in 1.5.8. Upgrade to this version or later.
Is CVE-2007-2637 exploitable, and should I be worried? Whether CVE-2007-2637 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2007-2637 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2007-2637? Upgrade moin to 1.5.8 or later.

Other vulnerabilities in moin

CVE-IDSeverityPackage summary

CVE-2008-6549Highmoin: MoinMoin Denial of Service vulnerability via password_checker function CVE-2008-6548Mediummoin: MoinMoin improper access control on the included page for the rst parser CVE-2010-2487Mediummoin: MoinMoin Cross-site Scripting (XSS) vulnerability CVE-2010-2970MediumMoin: MoinMoin cross-site scripting (XSS) vulnerability CVE-2010-2969Mediummoin: MoinMoin cross-site scripting (XSS) vulnerability