Security readout for executives and security teams
Plain-English summary
usememos memos v0.25.2 has an attachment-handling flaw: filenames are not sufficiently validated, allowing an authenticated attacker to traverse paths when interacting with attachments. Published impact is limited to low integrity impact, with no stated confidentiality or availability impact.
Executive priority
Treat as a moderate-priority application security issue. It needs timely remediation for exposed memos deployments, but current source data indicates authenticated access is required and impact is limited to integrity.
Technical view
CVE-2025-65799 is a CWE-73 path traversal issue in the Attachment service. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, indicating network reachability, low complexity, required privileges, and integrity-only impact.
Likely exposure
Exposure appears limited to deployments running usememos memos v0.25.2 where the Attachment service is reachable by authenticated users. The CVE record’s affected vendor/product fields are marked n/a, so confirm against the project advisory and PR.
Exploitation context
The source bundle does not report active exploitation, and CISA KEV status is false. Exploitation requires authenticated access according to the CVSS privileges-required value. No exploit details are included in the provided sources.
Researcher notes
Evidence is sparse: the CVE describes filename validation failure in the Attachment service, but the bundle does not provide exploit mechanics or a fixed version. Validate exposure against upstream code, the GitHub PR, and the USD advisory before concluding remediation status.
Mitigation direction
- Identify any usememos memos v0.25.2 deployments.
- Review the usememos PR and USD advisory for official remediation status.
- Apply vendor-recommended updates when a fixed release is confirmed.
- Restrict attachment functionality to trusted authenticated users where possible.
- Monitor attachment-related errors and unexpected file path behavior.
Validation and detection
- Inventory deployed memos versions and compare against v0.25.2.
- Review attachment handling configuration and access controls.
- Check logs for unusual attachment filename or path patterns.
- Confirm whether the referenced PR is present in deployed code.
- Track the CVE record for affected-version or fix updates.
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-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-65799 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:L/UI:N/S:U/C:N/I:L/A:N2.81.4CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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/usememos/memos/pull/5218CVE reference, mitre
- https://herolab.usd.de/security-advisories/usd-2025-0056/CVE 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.
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.