Skip to content
Fencer Intel
medium 4.7

CVE-2026-120743 json

Simply Schedule Appointments <= 1.6.13.4 - Unauthenticated Stored Cross-Site Scripting via 'payment_method' Parameter

published 18h ago modified 17h ago also EUVD-2026-132075

cvss
4.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

The Simply Schedule Appointments plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'payment_method' parameter in all versions up to, and including, 1.6.13.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The stored payload is only rendered when an administrator navigates to the hidden support page (/wp-admin/admin.php?ssa-support-admin=1) and triggers the 'Fix appointment durations' action, a condition reliably engineered by the attacker by smuggling a '+1 day' suffix in the start_date field to create a persistent duration mismatch that routes the malicious booking through the vulnerable echo path. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.

Is CVE-2026-120743 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-21).

CVSS scores

assigned by version score vector
CNA 3.1 4.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 3.1 4.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected products

  • croixhaug Simply Schedule Appointments

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.