# CVE-2024-3231: Popup4Phone <= 1.3.2 - Unauthenticated Stored XSS

> Unauthenticated attackers can inject malicious scripts via unsanitized parameters, potentially compromising admin accounts in the Popup4Phone WordPress plugin.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 17 May 2024
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-xq5f-88w9-ffw2

## What is CVE-2024-3231?

CVE-2024-3231 is a medium-severity cross-site scripting vulnerability in Unknown Popup4Phone, published on 17 May 2024. 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

The Popup4Phone WordPress plugin through 1.3.2 does not sanitise and escape some parameters, which could allow unauthenticated users to perform Cross-Site Scripting attacks against admins.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Ivanweb Popup4phone.

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

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

## Is CVE-2024-3231 being exploited?

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

Public exploit code:

- Popup4Phone <= 1.3.2 - Unauthenticated Stored Cross-Site Scripting (nuclei): http/cves/2024/CVE-2024-3231.yaml

## Other vulnerabilities in Unknown Popup4Phone

- [CVE-2024-3580](https://insights.sbomify.com/CVE-2024-3580/): Popup4Phone <= 1.3.2 - Editor+ Stored XSS (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3231 is a medium-severity cross-site scripting vulnerability in Unknown Popup4Phone, published on 17 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3231 exists.

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

## Sources

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

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