CVE-2024-13099: The Widget4Call WordPress plugin through 1.0.7 does not sanitise and escape a parameter before outputting it b

Q: How do I fix CVE-2024-13099?

widget4call: upgrade to newer than 1.0.7. Exact commands for each OS are on this page.

Q: Is CVE-2024-13099 being exploited?

CVE-2024-13099 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-13099 affect?

CVE-2024-13099 affects widget4call. Severity is medium (CVSS 5.4). 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.

Q: How urgent is CVE-2024-13099?

Priority 37/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2024-13099 is a medium-severity flaw (CVSS 5.4) affecting widget4call. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-02-01
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: apidaze

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-01 06:15 UTCPublished CVE record published
2026-06-17 07:01 UTCUpdated Record last modified

apidaze widget4call UPGRADE

Affected: <= 1.0.7

Fixed in: newer than 1.0.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy widget4call || rpm -q widget4call || widget4call --version

2. UPGRADE to newer than 1.0.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade widget4call

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade widget4call

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: Widget4Call WordPress - Cross-Site Scripting

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-13099?

widget4call: upgrade to newer than 1.0.7. Exact commands for each OS are on this page.

Is CVE-2024-13099 being exploited?

CVE-2024-13099 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-13099 affect?

CVE-2024-13099 affects widget4call. Severity is medium (CVSS 5.4). 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.

How urgent is CVE-2024-13099?

Priority 37/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-5727 MEDIUM 4.7 UPGRADE The Widget4Call WordPress plugin through 1.0.7 does not sanitise and escape a parameter before outputting it b

References

← Back to latest CVEs