WordPress Restaurant Menu Plugin Stored XSS via Phone Number

The Restaurant Menu and Food Ordering plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'phone_number' parameter in all versions up to, and including, 2.4.14 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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The Restaurant Menu and Food Ordering plugin for WordPress contains a Stored Cross-Site Scripting (XSS) vulnerability in the 'phone_number' parameter affecting all versions through 2.4.14. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious JavaScript that persists in the database. When any user visits a page containing the injected payload, the script executes in their browser with their privileges, potentially enabling account takeover, credential theft, malware distribution, or defacement. Organizations running this plugin—particularly small restaurants and food service businesses relying on WordPress for ordering functionality—face immediate risk without patching to version 2.4.15 or later.

Casky's 323 mapped security skills leverage Claude AI's extended reasoning to detect the attack patterns underlying this vulnerability across MITRE ATT&CK Initial Access (TA0001) and Resource Development (TA0043) techniques. Practitioners using Casky would observe detections flagging insufficient input validation on web form parameters, particularly CWE-79 patterns where user-supplied data reaches the DOM without proper encoding. The platform's skills would identify stored payload persistence mechanisms and highlight dangerous output contexts where unsanitized data renders as executable HTML/JavaScript. Security teams would see findings correlating suspicious database writes to the phone_number field with subsequent page rendering anomalies, enabling them to identify compromised installations and trace which pages contain active payloads before users are affected.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-96568.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-96568

Casky has 323 skills that investigate the attack patterns behind CVE-2026-96568. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn