dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-47918

MEDIUM · 6.1 CVSS v3.1 Published 2024-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Tiki Wiki CMS – CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

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

A Cross-Site Scripting (XSS) vulnerability (CWE-80) in Tiki Wiki CMS allows attackers to inject malicious HTML/script tags into web pages, potentially stealing session cookies or performing actions on behalf of authenticated users.

MitigationImplement proper input validation and output encoding/sanitization for all user-supplied data before rendering in HTML context.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Identify Tiki Wiki version
    Check the version by viewing the page footer, accessing the admin control panel (tiki-admin.php), or locating the version file in the installation directory
    Affected if The installed version matches the vulnerable version range published by Tiki Wiki for this CVE
  2. Confirm user input features are enabled
    Identify if the site has user-contributed content features active such as wiki pages, comments, forums, trackers, or blogs where users can submit content
    Affected if User-supplied input can be submitted and displayed on the site without additional verification
  3. Locate the vulnerable input point
    Review the CVE details from Tiki Wiki bug tracker to identify the specific parameter, module, or feature where the XSS occurs (such as a specific field in wiki editing, comments, or user profile)
    Affected if The identified vulnerable parameter or feature is present and accessible on your installation
  4. Test for XSS vulnerability
    Using a safe test string (such as a benign HTML tag or script alert) in the identified vulnerable parameter, submit the input and verify whether it is rendered as raw HTML or properly escaped when the page displays it
    Affected if The submitted HTML/script tags are rendered unescaped in the output, indicating the XSS vulnerability is present and exploitable

Your environment is affected if the installed Tiki Wiki version falls within the vulnerable range and user-contributed content containing the specific vulnerable parameter can be submitted and is rendered without proper encoding.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding/sanitization for all user-supplied data before rendering in HTML context.

Have this fixed 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 help mitigating

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-2024-47918 — 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-2024-47918 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