CVE-2025-52463VulnerabilityPublished 2 Jul 2025

CVE-2025-52463: QUALITIA Active! mail 6 · Cross-site request forgery (CSRF)

Affects QUALITIA Active! mail 6Source CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

3.1Low

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

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

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: None: There is no loss of confidentiality within 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 2 Jul 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 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

Affected software

Product	Affected	Fixed in
QUALITIA CO., LTD. Active! mail 6	Affected <=6.60.06008562	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should apply any available patches or updates from QUALITIA CO., LTD. that address this CSRF issue. In the absence of patches, implementing anti-CSRF tokens in all state-changing requests, especially those that trigger email sending, is critical. Organizations should also enforce strict Content Security Policies (CSP) and SameSite cookie attributes to reduce the risk of CSRF attacks. User education is important to reduce the likelihood of clicking on suspicious links, especially those received via email or external sources. Additionally, monitoring outgoing email traffic for unusual patterns or volumes can help detect exploitation attempts. Network-level controls such as web application firewalls (WAFs) can be configured to detect and block suspicious requests that resemble CSRF attack patterns. Finally, restricting the use of Active! mail 6 to trusted networks or VPNs can reduce exposure.

Description

Cross-site request forgery vulnerability exists in Active! mail 6 BuildInfo: 6.60.06008562 and earlier. If this vulnerability is exploited, unintended E-mail may be sent when a user accesses a specially crafted URL while being logged in.

Impact

For European organizations using Active! mail 6, this vulnerability could lead to unauthorized emails being sent from legitimate user accounts. This could result in reputational damage, especially if the emails are used for phishing or spam campaigns that appear to originate from trusted internal sources. It may also lead to internal confusion or operational disruptions if automated processes rely on email communications. However, the low severity and requirement for user interaction limit the overall risk. Organizations with strict email policies or regulatory requirements around email integrity (e.g., GDPR implications if personal data is involved in the emails) should be cautious. Attackers could exploit this vulnerability to send misleading or malicious emails, potentially facilitating further social engineering attacks within the organization.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Jul 2025, 05:24 UTC

Technical details

References

Community reviews

Related threats