LiveActive security incident?Get immediate response
CVE Record

CVE-2024-0849: Leanote 2.7.0 - Local File Read

Leanote version 2.7.0 allows obtaining arbitrary local files. This is possible because the application is vulnerable to LFR.

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Leanote 2.7.0 has a local file read issue that can expose files from a user’s machine. The published scoring requires local access, low privileges, and user interaction, so this is not described as a broad remote internet exploit. The main business risk is confidentiality loss on endpoints where Leanote handles sensitive data or runs near secrets.

Executive priority

Treat this as a targeted confidentiality risk rather than an emergency internet-wide exposure. Prioritize remediation where Leanote 2.7.0 is used on endpoints containing credentials, customer data, source code, or operational secrets.

Technical view

CVE-2024-0849 affects Leanote 2.7.0 and is classified as CWE-22. The CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N, giving a 5.0 medium score. The source description says arbitrary local files can be obtained through local file read behavior.

Likely exposure

Exposure appears limited to environments running Leanote 2.7.0, especially desktop or local-user contexts. The sources do not identify other affected versions, hosted deployments, or internet-facing attack paths. Organizations not using Leanote 2.7.0 are not shown as affected by the provided data.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not state active exploitation. The CVSS vector indicates exploitation requires local attack conditions, low privileges, and user interaction. Evidence supports confidentiality impact only; integrity and availability impacts are not indicated.

Researcher notes

The public bundle gives limited technical detail beyond arbitrary local file read, CWE-22, and the CVSS vector. Do not assume a remote route, exploit maturity, affected versions beyond 2.7.0, or a specific fix unless vendor or advisory updates confirm them.

Mitigation direction

  • Inventory systems for Leanote 2.7.0 installations.
  • Check Leanote and Fluid Attacks guidance for fixed versions or vendor remediation.
  • Remove or restrict Leanote 2.7.0 where sensitive local files are present.
  • Apply least privilege to accounts using affected Leanote installations.
  • Avoid opening untrusted content in affected Leanote environments.

Validation and detection

  • Confirm whether Leanote 2.7.0 is installed on managed endpoints.
  • Review endpoint profiles for local secrets accessible to Leanote users.
  • Check vendor and advisory pages for remediation status.
  • Validate any upgrade or workaround in a controlled environment.
  • Record non-affected systems with version evidence.
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-22: 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 lookup
cve · low confidence lookup

CVE-2024-0849 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 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/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
0Timeline events
0ADP providers
3Source links

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
5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N1.33.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5Medium
CVSS 3.1 vector shape for CVE-2024-0849Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LeanoteLeanote2.7.0unaffected
Weakness

CWE details

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

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.