# CVE-2020-29007: Code injection in n/a

> Attackers with edit permissions can execute arbitrary code via crafted musical score inputs in the MediaWiki Score extension.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2023
- **Updated:** 6 Feb 2025
- **Also known as:** GHSA-v67w-wjqm-h9pj

## What is CVE-2020-29007?

CVE-2020-29007 is a critical code injection vulnerability in n/a, published on 15 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Score extension through 0.3.0 for MediaWiki has a remote code execution vulnerability due to improper sandboxing of the GNU LilyPond executable. This allows any user with an ability to edit articles (potentially including unauthenticated anonymous users) to execute arbitrary Scheme or shell code by using crafted {{Image data to generate musical scores containing malicious code.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Mediawiki Score.

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

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

## Is CVE-2020-29007 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-29007 exists.

Public exploit code:

- Remote code execution in Mediawiki Score (github_poc): https://github.com/seqred-s-a/cve-2020-29007

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29007 is a critical code injection vulnerability in n/a, published on 15 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-29007 exists.

Affected product: n/a. 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-29007/ (Markdown: https://insights.sbomify.com/CVE-2020-29007/index.md)
```

## Sources

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

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