# CVE-2020-29254: Cross-site request forgery in n/a

> An attacker can trick a user into editing templates via CSRF, leading to arbitrary code execution and privilege escalation in TikiWiki.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6rxh-rgmc-47h8

## What is CVE-2020-29254?

CVE-2020-29254 is a high-severity vulnerability in Tiki Tikiwiki Cms\/Groupware, published on 11 Dec 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

TikiWiki 21.2 allows templates to be edited without CSRF protection. This could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack and perform arbitrary actions on an affected system. The vulnerability is due to insufficient CSRF protections for the web-based management interface of the affected system. An attacker could exploit this vulnerability by persuading a user of the interface to follow a maliciously crafted link. A successful exploit could allow the attacker to perform arbitrary actions on an affected system with the privileges of the user. These action include allowing attackers to submit their own code through an authenticated user resulting in local file Inclusion. If an authenticated user who is able to edit TikiWiki templates visits an malicious website, template code can be edited.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2020-29254?

It affects 1 product.


Products: Tiki Tikiwiki Cms\/Groupware.

## How do I fix CVE-2020-29254?

No fix has been published for CVE-2020-29254 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-29254 being exploited?

There is no known exploitation of CVE-2020-29254 in the wild and no public exploit code.

Public exploit code:

- TikiWiki 21.2 allows to edit templates without the use of a CSRF protection.  (github_poc): https://github.com/S1lkys/CVE-2020-29254

## Other vulnerabilities in Tiki Tikiwiki Cms\/Groupware

- [CVE-2008-3653](https://insights.sbomify.com/CVE-2008-3653/): Multiple unspecified vulnerabilities in TikiWiki CMS/Groupware before 2.0 have unknown impact and attack vectors. (critical 10.0)
- [CVE-2007-6529](https://insights.sbomify.com/CVE-2007-6529/): Other in n/a (critical 10.0)
- [CVE-2010-4239](https://insights.sbomify.com/CVE-2010-4239/): Path traversal in CMS Groupware (critical 9.8)
- [CVE-2012-0911](https://insights.sbomify.com/CVE-2012-0911/): Deserialization in n/a (critical 9.8)
- [CVE-2025-34111](https://insights.sbomify.com/CVE-2025-34111/): Tiki Wiki <= 15.1 ELFinder Unauthenticated File Upload RCE (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-29254 and fix it if it is affected.

What it is: CVE-2020-29254 is a high-severity vulnerability in Tiki Tikiwiki Cms\/Groupware, published on 11 Dec 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-29254 in the wild and no public exploit code.

Affected product: Tiki Tikiwiki Cms\/Groupware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-29254/ (Markdown: https://insights.sbomify.com/CVE-2020-29254/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-29254
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-29254
- OSV: https://osv.dev/vulnerability/CVE-2020-29254

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-29254/
Summaries are generated and may contain mistakes; the official description above is the record.