dbcve.org
MoinmoinApplication

CVE-2008-1099

MEDIUM · 5.0 CVSS v2.0 Published 2008-03-05
Fix available
A fix is available. Upgrade to after 1.5.8 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
_macro_Getval in wikimacro.py in MoinMoin 1.5.8 and earlier does not properly enforce ACLs, which allows remote attackers to read protected pages.

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 confidence

The _macro_Getval function in wikimacro.py in MoinMoin 1.5.8 and earlier fails to properly enforce Access Control Lists (ACLs), allowing remote unauthenticated attackers to read protected pages that should be restricted based on ACL rules.

MitigationUpgrade MoinMoin to a version newer than 1.5.8, or apply a patch to wikimacro.py that ensures _macro_Getval properly validates ACL permissions before returning page content.

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
MoinmoinApplication
Affected:<= 1.5.8

CVSS 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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MoinMoin installation and version
    Locate the MoinMoin installation directory and check the version.py or VERSION file. Common locations include /usr/lib/python*/site-packages/MoinMoin/ or a wiki-specific installation directory. Run: python -c 'import MoinMoin; print MoinMoin.__version__' or inspect the version file.
    Affected if The installed version is 1.5.8 or any version lower than 1.5.8
  2. Locate and inspect wikimacro.py
    Find wikimacro.py within the MoinMoin installation (typically in the MoinMoin directory). Open the file and search for the function definition '_macro_Getval' or 'Getval'.
    Affected if The file exists and contains the _macro_Getval function without proper ACL validation logic around line 80-120 (the exact lines vary by patch version)
  3. Verify ACL configuration exists
    Check the wiki's configuration (wikiconfig.py or farmconfig.py) for any ACL settings. Also check if any pages have ACL lines defined (these typically appear at the top of wiki pages as '#acl someuser:read').
    Affected if ACL rules are defined in the wiki configuration or on individual pages, indicating the wiki relies on access controls that should restrict certain pages
  4. Confirm unauthenticated access is possible
    Attempt to access the wiki without providing credentials. If the wiki allows read access to anonymous/guest users, verify whether the Getval macro can be invoked via URL or by creating a test page that calls the macro.
    Affected if The wiki accepts unauthenticated connections and allows viewing or creating pages without login, enabling the attack vector
  5. Test for vulnerable macro exposure
    Create a test wiki page (or inspect existing pages) containing {{Getval(page name, field name)}} or similar macro syntax that calls _macro_Getval. Try accessing a page you know should be ACL-protected.
    Affected if The Getval macro executes and returns content from pages that should be restricted by ACL rules, demonstrating the vulnerability in use

You are affected if running MoinMoin version 1.5.8 or earlier AND the wiki allows unauthenticated access AND ACLs are defined to restrict certain pages, as the _macro_Getval function can bypass these restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.5.8
Interim mitigation

Upgrade MoinMoin to a version newer than 1.5.8, or apply a patch to wikimacro.py that ensures _macro_Getval properly validates ACL permissions before returning page content.

Fix this in Moinmoin Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-1099 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-1099 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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