KonawikiApplication · Kujirahand

CVE-2021-20721

CRITICAL · 9.8 CVSS v3.1 Published 2021-05-20
Fix available
A fix is available. Upgrade to 2.2.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
KonaWiki2 versions prior to 2.2.4 allows a remote attacker to upload arbitrary files via unspecified vectors. If the file contains PHP scripts, arbitrary code may be executed.

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

KonaWiki2 versions before 2.2.4 contains an arbitrary file upload vulnerability allowing unauthenticated remote attackers to upload any file type to the server. If the uploaded file contains PHP code, the attacker can achieve remote code execution by requesting the uploaded file.

MitigationUpgrade to KonaWiki2 version 2.2.4 or later. If immediate upgrade is not feasible, disable file upload functionality and/or implement server-side restrictions on file types (whitelist approach) to prevent executable files from being stored.

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
KonawikiApplication
Affected:< 2.2.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installed KonaWiki2 version
    Locate the version file or admin panel that displays the KonaWiki2 version number, typically found in the application header, about page, or version configuration file
    Affected if The installed version is lower than 2.2.4
  2. Verify file upload functionality is present
    Access the wiki and look for file upload options, typically found in page editing tools, attachments section, or a dedicated upload interface
    Affected if File upload functionality exists and is accessible to users
  3. Check if upload endpoint allows unauthenticated access
    Attempt to access the file upload script/endpoint without logging in - common paths include /index.php with upload action, /attach/, or similar upload-related URLs
    Affected if The upload endpoint accepts requests without requiring authentication
  4. Confirm uploaded files are web-accessible
    After uploading a test file (or reviewing upload configuration), verify the files are stored in a web-accessible directory and can be requested via HTTP
    Affected if Uploaded files are stored in a web-accessible directory and can be directly requested via browser or curl

You are affected if running KonaWiki2 version below 2.2.4 AND file upload functionality is enabled and accessible without authentication, allowing attackers to upload executable files to a web-accessible location.

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.

dbcve · scoped
Upgrade available Upgrade to 2.2.4 or later
Fixed in 2.2.4
Interim mitigation

Upgrade to KonaWiki2 version 2.2.4 or later. If immediate upgrade is not feasible, disable file upload functionality and/or implement server-side restrictions on file types (whitelist approach) to prevent executable files from being stored.

Recommended fix Moderate confidence

2.2.4

  1. Confirm current installed version of KonaWiki2
  2. Download KonaWiki2 version 2.2.4 from the official source (kujirahand.com)
  3. Back up the existing database and all wiki files
  4. Replace existing files with the new version 2.2.4 files
  5. Verify the upgrade was successful by checking the version number in the admin interface
  6. Test file upload functionality to confirm the vulnerability is patched

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Konawiki Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20721 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-20721 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