CVE-2025-62902
7.5ThemeHunk · WP Popup Builder
ThemeHunk WP Popup Builder is vulnerable to sensitive information exposure, allowing unauthenticated attackers to retrieve embedded system data.
Executive summary
An unauthenticated information exposure vulnerability in the ThemeHunk WP Popup Builder plugin poses a significant risk of unauthorized data access.
Vulnerability
This flaw, categorized under CWE-497, allows an unauthenticated attacker to remotely access sensitive system information embedded within the plugin by interacting with the affected endpoint. The vulnerability is fully automatable, requiring no user interaction or prior authentication to exploit.
Business impact
The exposure of sensitive system information can provide attackers with the reconnaissance data necessary to conduct further, more sophisticated attacks against the WordPress environment. Given the CVSS score of 7.5, this vulnerability represents a high risk to organizational security, potentially leading to unauthorized disclosure of internal configuration details or environment-specific data.
Remediation
Immediate Action: Review the official ThemeHunk security advisories for the release of a patched version of WP Popup Builder and update immediately. If a patch is unavailable, consider disabling the plugin until a secure version is released.
Proactive Monitoring: Review web server and WordPress access logs for anomalous requests targeting the plugin directory, particularly those originating from unknown or suspicious IP addresses.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block unauthorized requests to the WP Popup Builder plugin endpoints to mitigate potential exploitation attempts.
Exploitation status
Public Exploit Available: Unknown.
Analyst recommendation
Organizations utilizing the ThemeHunk WP Popup Builder plugin should prioritize this vulnerability for remediation, given the ease with which an unauthenticated attacker can extract system data. Until a vendor patch is confirmed and applied, restricting access to the affected site or disabling the plugin is the most effective method to prevent potential data compromise.
More ThemeHunk CVEs
Sources
Originally found and disclosed by Bao - BlueRock | Patchstack Bug Bounty Program, per the CVE Program record.