CVE-2025-70758VulnerabilityPublished 3 Feb 2026Updated 11 Feb 2026

CVE-2025-70758: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 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-25.

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

AI-suggested

To mitigate CVE-2025-70758, developers must update the includes/auth_validate.php file to ensure that exit() or die() is called immediately after sending the HTTP redirect header to login.php, preventing further script execution. Conduct a thorough code review of all redirect and authentication logic to confirm proper termination after redirects. Implement robust access control checks on all protected pages to verify authentication status server-side before rendering sensitive content. Employ security testing tools such as static code analyzers and penetration testing to detect similar issues. Organizations should monitor web server logs for unusual access patterns to protected resources. If patching is not immediately possible, consider deploying web application firewalls (WAFs) with rules to block unauthenticated access attempts to admin panel URLs. Educate developers on secure PHP coding practices, particularly regarding header management and session validation.

Description

CVE-2025-70758 is an authentication bypass vulnerability in the chetans9 core-php-admin-panel due to improper handling of HTTP redirects in includes/auth_validate.php. The application redirects unauthenticated users to login.php but fails to terminate execution afterward, allowing attackers to access protected pages without credentials. This flaw can expose sensitive customer database information. The vulnerability has a high CVSS score of 7.5, indicating significant confidentiality impact with no user interaction or privileges required. No known exploits are currently in the wild. European organizations using this admin panel or similar PHP-based management tools are at risk, especially those handling sensitive customer data. Mitigation requires code fixes to ensure exit() is called after redirects and thorough access control validation.

Impact

For European organizations, this vulnerability poses a substantial risk to the confidentiality of customer data managed via the affected admin panel. Unauthorized access to protected pages can lead to data leakage, regulatory non-compliance (e.g., GDPR violations), and reputational damage. Organizations in sectors such as e-commerce, finance, healthcare, and public services that rely on PHP-based admin panels for customer management are particularly vulnerable. The ease of exploitation without authentication or user interaction increases the likelihood of automated attacks or scanning by threat actors. Additionally, the exposure of sensitive customer information can facilitate further attacks like phishing, identity theft, or fraud. The impact is amplified in countries with stringent data protection laws, where breaches can result in heavy fines and legal consequences.

CWE-703Improper Check or Handling of Exceptional Conditions (opens in a new tab)
Pillar weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 18 Feb 2026, 15:07 UTC

WeaknessesCWE-703

Technical details

References

Community reviews

Related threats