GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GHSA-vhm8-wwrf-3gcwmedium6.5

Path Traversal Vulnerability in `LESS` Parser allows reading of sensitive server files

Check your stack

The advisory, in context

Impact

If an admin account has already been compromised by an attacker, the LESS parser can be exploited to read sensitive files on the server through the use of path traversal techniques.

An attacker can achieve this by providing an absolute path to a sensitive file in the custom LESS setting, which the LESS parser will then read. For example, an attacker could use the following code to read the contents of the /etc/passwd file:

@import (inline) '/etc/passwd';

.test {
  content: data-uri('/etc/passwd');
}

Patches

The vulnerability has been addressed in version 1.7. Users should upgrade to this version to mitigate the vulnerability.

Workarounds

Users can mitigate the vulnerability by ensuring that their admin accounts are secured with strong passwords and other best practices for account security. Additionally, users can limit the exposure of sensitive files on the server by implementing appropriate file permissions and access controls.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

flarum/core Packagist
Ecosystem versions

Earlier releases before 1.7.0

Fixed in 1.7.0

40 explicitly affected versions

v0.1.0-beta, v0.1.0-beta.10, v0.1.0-beta.11, v0.1.0-beta.11.1, v0.1.0-beta.12, v0.1.0-beta.13, v0.1.0-beta.14, v0.1.0-beta.14.1, v0.1.0-beta.15, v0.1.0-beta.16, v0.1.0-beta.2, v0.1.0-beta.3, v0.1.0-beta.4, v0.1.0-beta.5, v0.1.0-beta.6, v0.1.0-beta.7, v0.1.0-beta.7.1, v0.1.0-beta.7.2, v0.1.0-beta.8, v0.1.0-beta.8.1, v0.1.0-beta.8.2, v0.1.0-beta.9, v1.0.0, v1.0.1, v1.0.2, v1.0.3, v1.0.4, v1.1.0, v1.1.1, v1.2.0, v1.2.1, v1.3.0, v1.3.1, v1.4.0, v1.4.1, v1.5.0, v1.6.0, v1.6.1, v1.6.2, v1.6.3

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.7.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v0.1.0-beta",
    "v0.1.0-beta.10",
    "v0.1.0-beta.11",
    "v0.1.0-beta.11.1",
    "v0.1.0-beta.12",
    "v0.1.0-beta.13",
    "v0.1.0-beta.14",
    "v0.1.0-beta.14.1",
    "v0.1.0-beta.15",
    "v0.1.0-beta.16",
    "v0.1.0-beta.2",
    "v0.1.0-beta.3",
    "v0.1.0-beta.4",
    "v0.1.0-beta.5",
    "v0.1.0-beta.6",
    "v0.1.0-beta.7",
    "v0.1.0-beta.7.1",
    "v0.1.0-beta.7.2",
    "v0.1.0-beta.8",
    "v0.1.0-beta.8.1",
    "v0.1.0-beta.8.2",
    "v0.1.0-beta.9",
    "v1.0.0",
    "v1.0.1",
    "v1.0.2",
    "v1.0.3",
    "v1.0.4",
    "v1.1.0",
    "v1.1.1",
    "v1.2.0",
    "v1.2.1",
    "v1.3.0",
    "v1.3.1",
    "v1.4.0",
    "v1.4.1",
    "v1.5.0",
    "v1.6.0",
    "v1.6.1",
    "v1.6.2",
    "v1.6.3"
  ]
}

References