dbcve.org
IkiwikiApplication

CVE-2011-0428

MEDIUM · 6.1 CVSS v3.1 Published 2019-10-29
Fix available
A fix is available. Upgrade to 3.20110122 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross Site Scripting (XSS) in ikiwiki before 3.20110122 could allow remote attackers to insert arbitrary JavaScript due to insufficient checking in comments.

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 · high confidence

Cross-site scripting (XSS) vulnerability in ikiwiki's comment processing function before version 3.20110122 allows remote attackers to inject arbitrary JavaScript code due to insufficient input validation and sanitization of comment content submitted to the wiki.

MitigationUpgrade ikiwiki to version 3.20110122 or later, which implements proper input sanitization and output encoding for comment content to prevent XSS injection.

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
IkiwikiApplication
Affected:< 3.20110122

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
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check installed ikiwiki version
    Run 'ikiwiki --version' or check the package manager (dpkg -l ikiwiki, rpm -q ikiwiki)
    Affected if Version is below 3.20110122
  2. Verify comments plugin is enabled
    Inspect ikiwiki setup file (usually ~/.ikiwiki/ikiwiki.yaml or /etc/ikiwiki/ikiwiki.conf) for 'add_plugins' or 'comments' configuration
    Affected if Comments plugin is listed in enabled plugins
  3. Confirm comment form is active
    Check the wiki's configuration for 'comments' directive or presence of comment page templates in the wiki source
    Affected if Comments are actively processed by the wiki
  4. Inspect comment input handling
    Examine the ikiwiki CGI script or comment processing code to verify lack of sanitization on comment submission
    Affected if Comment content is processed without proper HTML escaping or sanitization

If ikiwiki version is below 3.20110122 AND the comments feature is enabled, the environment is vulnerable to XSS via comment injection.

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 3.20110122 or later
Fixed in 3.20110122
Interim mitigation

Upgrade ikiwiki to version 3.20110122 or later, which implements proper input sanitization and output encoding for comment content to prevent XSS injection.

Fix this in Ikiwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-0428 — 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-2011-0428 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