CVE-2025-15422
Protection Bypass in EmpireCMS IP Address Handler (egetip
Publication date: 2026-01-02
Last updated on: 2026-01-02
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| empiresoft | empirecms | to 8.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-693 | The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15422 is an IP address spoofing vulnerability in EmpireSoft EmpireCMS up to version 8.0. It exists in the function egetip() within the file e/class/connect.php, which determines the client's IP address by prioritizing user-controllable HTTP headers (HTTP_CLIENT_IP and HTTP_X_FORWARDED_FOR) over the more reliable REMOTE_ADDR server variable. Because these headers can be manipulated by an attacker remotely without authentication, this flaw allows attackers to spoof IP addresses, bypass IP-based protections, and falsify IP information recorded in logs and databases. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing remote attackers to bypass IP-based access controls such as login attempt limits, IP whitelists/blacklists, and rate limiting. Attackers can spoof IP addresses to evade brute-force protections and rotate spoofed IPs for each login attempt. It also enables falsification of IP addresses in security logs and databases, complicating forensic investigations and potentially allowing privilege escalation by circumventing security restrictions that rely on accurate client IP identification. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for requests to the vulnerable file e/class/connect.php, especially those containing suspicious or spoofed HTTP headers such as HTTP_CLIENT_IP or HTTP_X_FORWARDED_FOR. One detection method is to monitor web server logs for requests to URLs containing 'inurl:e/class/connect.php' and check if these headers are present or manipulated. Additionally, Google dorking with queries like 'inurl:e/class/connect.php' can help identify exposed vulnerable endpoints. Commands to detect suspicious requests might include using grep on web server logs, for example: grep 'e/class/connect.php' /var/log/apache2/access.log | grep -E 'HTTP_CLIENT_IP|HTTP_X_FORWARDED_FOR'. Network intrusion detection systems can also be configured to alert on unusual or spoofed IP header usage targeting this endpoint. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include modifying the vulnerable egetip() function in e/class/connect.php to prioritize the REMOTE_ADDR server variable over user-controllable HTTP headers like HTTP_CLIENT_IP and HTTP_X_FORWARDED_FOR. Forwarded headers should only be used in trusted proxy environments with proper validation. Since no official patches or vendor responses are available, consider replacing or upgrading the affected EmpireCMS component or product. Additionally, monitor and restrict access to the vulnerable endpoint and implement network-level protections such as web application firewalls to block suspicious requests exploiting this flaw. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows attackers to spoof IP addresses, which can lead to falsification of security logs and database records. Such manipulation can hinder accurate audit trails and forensic investigations, potentially violating compliance requirements for data integrity and security under standards like GDPR and HIPAA. The inability to reliably track user activity and security events may result in non-compliance with regulations that mandate accurate logging and protection against unauthorized access. [2, 3]