Ratatouille <= 1.2.6 - Authenticated (Subscriber+) Server-Side Request Forgery
Strategic Overview
- Status
- Unpatched
- Affected Theme
- Restaurant WordPress Theme | Ratatouille
- Affected Version
<= 1.2.6- CVSS
- 6.4Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-28036
At a glance
CVE-2026-28036 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Restaurant WordPress Theme WordPress theme, affecting versions <= 1.2.6. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed March 2026, reported by Tran Nguyen Bao Khanh.
Vulnerability Overview
The Restaurant WordPress Theme | Ratatouille theme for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.2.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Restaurant WordPress Theme <= 1.2.6 takes an account at Subscriber level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. No fixed build of this theme is recorded for Restaurant WordPress Theme yet, so installs running <= 1.2.6 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C