Skip to main content
VulnerabilityPublished Updated

CVE-2024-51507: Tiki · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-51507, organizations should implement the following specific measures: 1) Restrict permissions carefully to limit which users can create or edit external wiki entries, minimizing the number of users who can inject content. 2) Apply strict input validation and output encoding on the 'Name' field and other user-supplied inputs within Tiki CMS to prevent script injection. 3) Monitor and audit changes to external wiki entries for suspicious or unexpected content. 4) Educate privileged users about the risks of stored XSS and encourage cautious behavior when editing content. 5) If possible, deploy web application firewalls (WAFs) with rules to detect and block XSS payloads targeting Tiki CMS. 6) Stay alert for official patches or updates from the Tiki CMS development team and apply them promptly once available. 7) Consider isolating or sandboxing the CMS environment to limit the impact of potential exploitation. These targeted actions go beyond generic advice by focusing on the specific vulnerability vector and user roles involved.

Description

Tiki through 27.0 allows users who have certain permissions to insert a "Create/Edit External Wiki" stored XSS payload in the Name.

References

Community reviews

Loading reviews…