VulnerabilityPublished 26 Aug 2025Updated 27 Aug 2025

CVE-2025-52218: Code Injection

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 2025.5.2 : patch affected systems soon.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.5.2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 26 Aug 2025
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 26 Oct 2026.

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-52218 effectively, European organizations should take the following specific actions: 1) Immediately upgrade the SelectZero Data Observability Platform to version 2025.5.2 or later once the patch is available, as this is the definitive fix for the vulnerability. 2) Until a patch is applied, implement web application firewall (WAF) rules to detect and block suspicious input patterns targeting the login page, focusing on injection attempts of HTML or script content. 3) Conduct thorough input validation and sanitization on all user-supplied parameters at the application level, ensuring that any embedded HTML or scripts are neutralized or escaped. 4) Educate users about the risk of phishing and spoofed login pages, encouraging verification of URLs and the use of multi-factor authentication (MFA) to reduce the risk of credential compromise. 5) Monitor logs and network traffic for anomalous activities related to the login page, such as unusual POST requests or injection payloads. 6) Coordinate with SelectZero support or vendor channels to obtain timely updates and security advisories. 7) Consider isolating the login interface behind additional authentication or VPN access to limit exposure to external attackers. These targeted measures go beyond generic advice by focusing on immediate protective controls and user awareness specific to this vulnerability's exploitation vector.

Description

SelectZero Data Observability Platform before 2025.5.2 is vulnerable to Content Spoofing / Text Injection. Improper sanitization of unspecified parameters allows attackers to inject arbitrary text or limited HTML into the login page.

Impact

For European organizations, the impact of CVE-2025-52218 can be substantial, especially for those relying on the SelectZero Data Observability Platform for monitoring and managing critical data infrastructure. The content spoofing vulnerability on the login page can be exploited to deceive legitimate users into submitting credentials or other sensitive information to attackers, leading to unauthorized access. This can compromise the integrity of data observability processes, potentially causing incorrect data monitoring, delayed detection of data issues, or manipulation of observability metrics. Such disruptions can affect decision-making, compliance reporting, and operational continuity. Furthermore, successful exploitation could serve as a foothold for further attacks within the organization's network. Given the platform's role in data observability, any compromise may also impact regulatory compliance under GDPR and other European data protection laws, exposing organizations to legal and reputational risks. The lack of confidentiality impact reduces the risk of direct data leakage via this vulnerability, but the high integrity impact and ease of exploitation elevate the threat level.

CWE-94Improper Control of Generation of Code ('Code Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #10OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Architecture and Design · Refactoring
Refactor your program so that you do not have to dynamically generate code.
Architecture and Design
Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V5.2.8 (opens in a new tab)
V5.2.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Leverage Executable Code in Non-Executable Files (opens in a new tab)
Manipulating User-Controlled Variables (opens in a new tab)
Code Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

selectzero.io/change-log/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Sep 2025, 01:09 UTC

WeaknessesCWE-94

Technical details

References

Community reviews

Related threats