CVE-2026-1812VulnerabilityPublished 3 Feb 2026Updated 23 Feb 2026

CVE-2026-1812: bolo-solo · Path Traversal

Affects bolo-soloSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
bolo-blogbolo-solo	Affected =2.6.0 =2.6.1 =2.6.2 =2.6.3 =2.6.4	Fixed in–
GitHubbolo-blog/bolo-solo`pkg:github/bolo-blog/bolo-solo`Other threats	Affected =2.6.0 =2.6.1 =2.6.2 =2.6.3 =2.6.4	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately audit their bolo-solo installations to determine if affected versions (2.6.0 to 2.6.4) are in use. Until an official patch is released, apply the following mitigations: 1) Restrict network access to the bolo-solo management interface using firewalls or VPNs to limit exposure. 2) Implement strict input validation and sanitization on the importFromCnblogs function or disable this feature if not required. 3) Employ web application firewalls (WAFs) with custom rules to detect and block path traversal patterns targeting the vulnerable endpoint. 4) Monitor server logs for suspicious file path access attempts indicative of traversal exploitation. 5) Isolate the bolo-solo server with least privilege principles and ensure backup files and sensitive data have restrictive permissions. 6) Regularly back up data and verify integrity to recover from potential tampering. 7) Stay alert for vendor updates or community patches and apply them promptly once available. 8) Consider migrating to alternative blogging platforms if timely remediation is not feasible. These targeted actions go beyond generic advice by focusing on access control, input filtering, and monitoring specific to the vulnerability context.

Description

A vulnerability has been found in bolo-blog bolo-solo up to 2.6.4. This impacts the function importFromCnblogs of the file src/main/java/org/b3log/solo/bolo/prop/BackupService.java of the component Filename Handler. The manipulation of the argument File leads to path traversal. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The path traversal vulnerability allows attackers to access files outside the intended directory structure, potentially exposing sensitive configuration files, user data, or application source code. This can lead to information disclosure, which may facilitate further attacks such as credential theft or privilege escalation. Integrity and availability impacts are considered low but cannot be ruled out if attackers modify files or disrupt backup processes. Organizations relying on bolo-solo for content management risk unauthorized data exposure and potential compromise of their web servers. Since the vulnerability is remotely exploitable without authentication or user interaction, attackers can automate exploitation at scale. The public disclosure of the exploit increases the risk of opportunistic attacks. The medium CVSS score reflects moderate severity, but the actual impact depends on the sensitivity of data stored and the deployment environment. Enterprises using bolo-solo in critical environments may face reputational damage, data breaches, and compliance violations if exploited.

Summary

CVE-2026-1812 is a path traversal vulnerability identified in the bolo-blog project's bolo-solo software, specifically affecting versions 2.6.0 through 2.6.4. The vulnerability resides in the importFromCnblogs function of the BackupService.java source file, part of the Filename Handler component. The flaw arises due to insufficient validation or sanitization of the file path argument passed to this function, enabling an attacker to manipulate the file parameter to traverse directories outside the intended scope. This can lead to unauthorized reading or potentially writing of files on the server hosting bolo-solo. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L - low privileges), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). bolo-solo is a blogging platform used primarily for personal or small to medium websites, which may store sensitive user content or configuration files vulnerable to exposure through this flaw.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:58 UTC

Technical details

References

Community reviews

Related threats