CVE-2025-15422VulnerabilityPublished 2 Jan 2026Updated 23 Feb 2026

CVE-2025-15422: EmpireSoft EmpireCMS · Protection Mechanism Failure

Affects EmpireSoft EmpireCMSSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
EmpireSoft EmpireCMS	Affected =8.0	Fixed in–

AI-suggested

1. Immediately restrict network access to the vulnerable EmpireCMS installation by implementing firewall rules or IP whitelisting to limit exposure to trusted sources only. 2. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the 'egetip' function or related IP address handling endpoints. 3. Monitor web server and application logs for unusual IP manipulation attempts or anomalies in IP-based access patterns. 4. Disable or isolate the IP Address Handler component if feasible without impacting critical functionality, until a vendor patch is available. 5. Conduct thorough security assessments and penetration testing focused on IP handling and access control mechanisms within EmpireCMS. 6. Prepare an incident response plan specific to this vulnerability, including rapid patch deployment once a fix is released. 7. Engage with the EmpireSoft community or security forums to track any unofficial patches or mitigation scripts. 8. Consider migrating to alternative CMS platforms if timely vendor support is unlikely and risk tolerance is low. 9. Educate administrators and developers about this vulnerability to avoid inadvertent exposure through configuration errors. 10. Regularly update and backup the CMS environment to enable quick recovery in case of compromise.

Description

A flaw has been found in EmpireSoft EmpireCMS up to 8.0. This issue affects the function egetip of the file e/class/connect.php of the component IP Address Handler. This manipulation causes protection mechanism failure. The attack may be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The vulnerability impacts organizations running EmpireCMS version 8.0 by undermining the IP address handling protection mechanisms. This can lead to attackers bypassing IP-based access controls or restrictions, potentially enabling unauthorized access or manipulation of web application behavior. The integrity of the system is primarily at risk, as attackers may alter or evade security policies relying on IP validation. Although the vulnerability does not directly affect confidentiality or availability, successful exploitation could serve as a stepping stone for more severe attacks, including privilege escalation or data tampering. The ease of remote exploitation without authentication or user interaction increases the threat level, especially for publicly accessible web servers. Organizations relying on EmpireCMS for critical web infrastructure may face reputational damage, data integrity issues, and increased risk of further compromise if this vulnerability is exploited. The absence of a vendor patch and the availability of a public exploit heighten the urgency to address this risk proactively.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 23:00 UTC

Technical details

References

Community reviews

Related threats