CVE-2010-0717
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMoinMoin before version 1.8.7 ships with an insecure default configuration for `cfg.packagepages_actions_excluded`, which fails to properly disable unsafe package-related actions. This configuration weakness could allow attackers to perform actions that should be restricted.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.8.6= 1.5.0= 1.5.1= 1.5.2= 1.5.3= 1.5.4= 1.5.5= 1.5.5a= 1.5.6= 1.5.7= 1.5.8= 1.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify MoinMoin installation and versionLocate the MoinMoin installation directory and check the version.py file, typically found in the MoinMoin package directory (e.g., /usr/lib/python*/site-packages/MoinMoin/version.py) or look for a version file within the wiki web application directory. Read the __version__ or version variable to determine the installed version.Affected if Installed version is 1.8.6 or earlier, or matches any of these specific versions: 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.5a, 1.5.6, 1.5.7, 1.5.8, or 1.6.0
-
Locate wiki configuration fileFind the wiki configuration file, typically named wikiconfig.py, wikiconfig_local.py, or farmconfig.py, located in the wiki data directory or the MoinMoin instance configuration directory (often under /etc/moin/ or within the web application root).Affected if Configuration file exists and is being used by the wiki instance
-
Check cfg.packagepages_actions_excluded settingOpen the wiki configuration file and search for the line defining 'packagepages_actions_excluded'. If this setting is not present, the default insecure configuration is in use. If present, examine whether it includes the unsafe actions that should be excluded.Affected if The setting is absent from the configuration (uses insecure default), or the setting does not properly exclude the unsafe package-related actions that should be blocked
You are affected if your MoinMoin installation matches any of the vulnerable versions listed AND your wiki configuration either lacks the packagepages_actions_excluded setting or uses a value that fails to exclude unsafe package-related actions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to MoinMoin 1.8.7 or later where the default configuration properly excludes unsafe package actions, or manually harden the `cfg.packagepages_actions_excluded` setting in the wiki configuration.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-0717 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data