# CVE-2024-13099: Widget4call <= 1.0.7 - Reflected XSS

> Reflected XSS in Widget4Call plugin allows attackers to execute scripts against admin users, potentially leading to account takeover.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-7fgp-fc75-5g7h

## What is CVE-2024-13099?

CVE-2024-13099 is a medium-severity cross-site scripting vulnerability in Unknown Widget4Call, published on 1 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Widget4Call WordPress plugin through 1.0.7 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

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

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

It affects 1 product.


Products: Apidaze Widget4call.

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

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

## Is CVE-2024-13099 being exploited?

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

Public exploit code:

- Widget4Call WordPress - Cross-Site Scripting (nuclei): http/cves/2024/CVE-2024-13099.yaml

## Other vulnerabilities in Unknown Widget4Call

- [CVE-2024-5727](https://insights.sbomify.com/CVE-2024-5727/): Widget4Call <= 1.0.7 - Reflected XSS (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13099 is a medium-severity cross-site scripting vulnerability in Unknown Widget4Call, published on 1 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-13099 exists.

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

## Sources

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

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