LiveActive security incident?Get immediate response
CVE Record

CVE-2025-65798: Incorrect access control in usememos memos v0.25.2 allows attackers with low-level privileges to arbitraril...

Incorrect access control in usememos memos v0.25.2 allows attackers with low-level privileges to arbitrarily modify or delete attachments made by other users.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A low-privileged user of usememos memos v0.25.2 may be able to change or delete attachments created by other users. The business concern is cross-user data tampering in a collaborative note system, not remote takeover. The source bundle does not name a fixed version.

Executive priority

Treat this as a moderate-priority integrity issue. It matters most for organizations relying on memos for shared notes, internal documentation, or user-uploaded attachments. Prioritize confirmation and patch tracking, especially on internet-accessible or broadly shared instances.

Technical view

CVE-2025-65798 is an incorrect access control issue, CWE-284, in usememos memos v0.25.2. CVSS 3.1 is 5.4: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is most likely where usememos memos v0.25.2 is deployed with multiple authenticated users and attachments. The structured affected-product fields are listed as n/a, so teams should confirm exact affected and fixed versions from upstream project guidance.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The described attacker already has low-level application privileges and can target other users' attachments through an access-control failure.

Researcher notes

Evidence is limited to the CVE metadata, upstream PR, and advisory links. The bundle does not provide exploit details, a fixed release, or complete structured affected-product data. Avoid assuming broader version impact without vendor confirmation.

Mitigation direction

  • Inventory usememos memos deployments and identify any running v0.25.2.
  • Review the upstream PR and advisory for official fixed-version guidance.
  • Restrict memos access to trusted users until remediation is confirmed.
  • Back up user attachments before applying upgrades or configuration changes.
  • Monitor attachment modification and deletion events for cross-user anomalies.

Validation and detection

  • Confirm deployed memos versions against v0.25.2 and vendor guidance.
  • Review application roles and attachment ownership enforcement.
  • Audit logs for attachment changes made by non-owners.
  • In authorized testing, verify users cannot alter another user's attachments.
  • Document whether a patched release or workaround has been applied.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookup
cve · low confidence lookup

CVE-2025-65798 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2025-65798Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.