# CVE-2020-8644: PlaySMS Server-Side Template Injection


- **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:** Yes, since 3 Nov 2021 (CISA KEV)
- **Fix available:** No
- **Published:** 5 Feb 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-q834-vxjw-r888

## What is CVE-2020-8644?

CVE-2020-8644 is a critical vulnerability in n/a, published on 5 Feb 2020. 

### Official description

PlaySMS before 1.4.3 does not sanitize inputs from a malicious string.

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

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

It affects 1 product.


Products: Playsms Playsms.

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

No fix has been published for CVE-2020-8644 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-8644 being exploited?

Yes. Attackers have exploited CVE-2020-8644 in the wild since at least 3 Nov 2021.

Public exploit code:

- Python script to exploit PlaySMS before 1.4.3 (github_poc): https://github.com/H3rm1tR3b0rn/CVE-2020-8644-PlaySMS-1.4
- PlaySMS index.php Unauthenticated Template Injection Code Execution (metasploit)
- PlaySMS - index.php Unauthenticated Template Injection Code Execution (Metasploit) (exploitdb)
- playSMS <1.4.3 - Remote Code Execution (nuclei): http/cves/2020/CVE-2020-8644.yaml

## Other vulnerabilities in n/a

- [CVE-2022-47034](https://insights.sbomify.com/CVE-2022-47034/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-40373](https://insights.sbomify.com/CVE-2021-40373/): Code injection in n/a (critical 9.8)
- [CVE-2017-9101](https://insights.sbomify.com/CVE-2017-9101/): File upload in n/a (critical 9.8)
- [CVE-2017-9080](https://insights.sbomify.com/CVE-2017-9080/): File upload in n/a (high 8.8)
- [CVE-2008-5881](https://insights.sbomify.com/CVE-2008-5881/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8644 is a critical vulnerability in n/a, published on 5 Feb 2020. 
Exploitation: Yes. Attackers have exploited CVE-2020-8644 in the wild since at least 3 Nov 2021.

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-8644/ (Markdown: https://insights.sbomify.com/CVE-2020-8644/index.md)
```

## Sources

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

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