# CVE-2024-6251: playSMS New Phonebook cross site scripting

> Attackers can inject malicious scripts via the phonebook name or email fields in playSMS, potentially compromising user sessions.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-3m77-f49c-p58r

## What is CVE-2024-6251?

CVE-2024-6251 is a medium-severity cross-site scripting vulnerability in playSMS, published on 22 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in playSMS 1.4.3. Affected is an unknown function of the file /index.php?app=main&inc=feature_phonebook&op=phonebook_list of the component New Phonebook Handler. The manipulation of the argument name/email leads to basic cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-269418 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2024-6251?

It affects 1 product.


Products: Playsms Playsms.

## How do I fix CVE-2024-6251?

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

## Is CVE-2024-6251 being exploited?

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

## Other vulnerabilities in playSMS

- [CVE-2020-8644](https://insights.sbomify.com/CVE-2020-8644/): PlaySMS Server-Side Template Injection (critical 9.8, exploited in the wild)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6251 and fix it if it is affected.

What it is: CVE-2024-6251 is a medium-severity cross-site scripting vulnerability in playSMS, published on 22 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6251 exists.

Affected product: playSMS. 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-2024-6251/ (Markdown: https://insights.sbomify.com/CVE-2024-6251/index.md)
```

## Sources

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

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