VulnerabilityPublished 31 Oct 2025

CVE-2025-30191: Malicious content from E-Mail can be used to perform a redressing attack

Source GCVE Database

Compare

Authoritative record:CVE-2025-30191· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 29 Oct 2026, 23:29 UTC

CVSS 3.1 base score

5.4Medium

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 on 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 31 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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.

ghsa-7p8g-rr59-8pqg

What to do

AI-suggested

A fix has been implemented by updating the sanitization procedure to deny attribute values containing HTML fragments. Users and administrators should ensure that this updated sanitization is applied. No additional immediate action is required as no public exploits are known and the vulnerability is mitigated by the sanitization update.

Description

CVE-2025-30191 is a medium severity vulnerability involving malicious email content that can be used to perform a redressing attack. This attack tricks users into performing unintended actions or disclosing sensitive information to third parties. The vulnerability arises from insufficient sanitization of attribute values containing HTML fragments, which has now been addressed by denying such values in the sanitization process. No public exploits are known at this time.

Impact

The impact includes potential user deception leading to unintended actions or disclosure of sensitive information to attackers, which could facilitate further malicious activities. The CVSS score of 5.4 (medium severity) reflects limited confidentiality and integrity impact without availability impact. No known exploitation in the wild reduces immediate risk.

Summary

This vulnerability allows malicious content embedded in emails to execute redressing attacks by exploiting insufficient sanitization of HTML fragments in attribute values. Users may be deceived into unintended interactions or leaking sensitive data to attackers, potentially enabling further threats. The sanitization procedure has been updated to deny attribute values containing HTML fragments, mitigating the risk. There are no known public exploits or active exploitation reported.

CWE-1021Improper Restriction of Rendered UI Layers or Frames (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.
Implementation
Use the "frame-ancestors" directive in the Content Security Policy, which is intended to define restrictions when it comes to allowing embedded content.
Implementation
The use of X-Frame-Options (now partially obsolete as of September 2026) allows developers of web content to restrict the usage of their application within the form of overlays, frames, or iFrames. The developer can indicate from which domains can frame the content.
Implementation
Use a "frame-breaker" script in each page that should not be framed. This is very helpful for legacy browsers that do not support the X-Frame-Options security feature previously mentioned (which is now partially obsolete).
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.3 (opens in a new tab)
V14.4.7 (opens in a new tab)
Attack patterns
Clickjacking (opens in a new tab)
Flash File Overlay (opens in a new tab)
iFrame Overlay (opens in a new tab)
Task Impersonation (opens in a new tab)
Tapjacking (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 29 Oct 2026, 23:29 UTC

WeaknessesCWE-1021

Technical details

References

Community reviews

Related threats