Security readout for executives and security teams
Plain-English summary
Blue Mail 1.140.103 and earlier may save opened attachments without Windows Mark-of-the-Web metadata. That missing tag can prevent Windows and security tools from applying normal downloaded-file protections, increasing the chance a malicious attachment is trusted too much.
Executive priority
Treat this as high-priority exposure triage if Blue Mail is present. The weakness affects a security boundary relied on by Windows and security tools, but the provided evidence does not prove active exploitation or identify an official patch.
Technical view
The CVE describes a CWE-693 protection-mechanism failure in Blue Mail attachment interaction. Saved documents lack Mark-of-the-Web tagging, enabling bypass of Windows and third-party file protection checks. The record assigns CVSS 3.1 score 9.1, with high confidentiality and integrity impact.
Likely exposure
Organizations are most exposed where Blue Mail 1.140.103 or earlier is used on Windows systems and users interact with email attachments. The source bundle does not provide CPEs, deployment scope, or platform-specific package identifiers.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. References include document-related attack tooling context, but the bundle does not establish real-world exploitation or a public weaponized chain for this CVE.
Researcher notes
The record’s affected-product fields are incomplete, listing n/a, while the description names Blue Mail 1.140.103 and below. Validate product identity, platform scope, fixed version, and reproducibility before broad conclusions. Do not infer exploit activity from reference links alone.
Mitigation direction
- Identify Blue Mail installations and versions across Windows endpoints.
- Prioritize upgrades or vendor guidance for Blue Mail 1.140.103 and earlier.
- Review endpoint controls for attachment handling and downloaded-file trust decisions.
- Increase monitoring for suspicious child processes from opened attachments.
- Avoid inventing compensating controls; confirm vendor-recommended remediation first.
Validation and detection
- Inventory Blue Mail versions and flag 1.140.103 or earlier.
- Confirm whether attachment-saved documents receive Mark-of-the-Web metadata.
- Check EDR logs for unusual attachment-open activity from Blue Mail.
- Review vendor advisories or release notes for a named fix.
- Document unsupported assumptions where affected CPE data is absent.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-65319 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/nickvourd/RTI-ToolkitCVE reference, mitre
- https://github.com/rip1s/CVE-2017-11882CVE reference, mitre
- https://drive.google.com/file/d/1dVzXuHBk3B1DiFpwFYwj2NNjeKGnGSwT/viewCVE reference, mitre
- https://github.com/bbaboha/CVE-2025-65318-and-CVE-2025-65319CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.