# CVE-2026-1813: bolo-blog bolo-solo FreeMarker Template PicUploadProcessor.java unrestricted upload

> Remote attackers can upload malicious files via the PicUploadProcessor, potentially leading to code execution on the bolo-solo blog server.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-2hmq-qjp7-8j88

## What is CVE-2026-1813?

CVE-2026-1813 is a medium-severity vulnerability in bolo-blog bolo-solo, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in bolo-blog bolo-solo up to 2.6.4. Affected is an unknown function of the file src/main/java/org/b3log/solo/bolo/pic/PicUploadProcessor.java of the component FreeMarker Template Handler. The manipulation of the argument File results in unrestricted upload. It is possible to launch the attack remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-1813?

It affects 1 product.


Products: Adlered Bolo-Solo.

## How do I fix CVE-2026-1813?

No fix has been published for CVE-2026-1813 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1813 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1813 exists.

## Other vulnerabilities in bolo-blog bolo-solo

- [CVE-2023-41009](https://insights.sbomify.com/CVE-2023-41009/): File upload in n/a (critical 9.8)
- [CVE-2026-1810](https://insights.sbomify.com/CVE-2026-1810/): bolo-blog bolo-solo ZIP File BackupService.java unpackFilteredZip path traversal (medium 5.3)
- [CVE-2026-1811](https://insights.sbomify.com/CVE-2026-1811/): bolo-blog bolo-solo Filename BackupService.java importFromMarkdown path traversal (medium 5.3)
- [CVE-2026-1812](https://insights.sbomify.com/CVE-2026-1812/): bolo-blog bolo-solo Filename BackupService.java importFromCnblogs path traversal (medium 5.3)
- [CVE-2026-1691](https://insights.sbomify.com/CVE-2026-1691/): bolo-solo SnakeYAML BackupService.java importMarkdownsSync deserialization (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1813 and fix it if it is affected.

What it is: CVE-2026-1813 is a medium-severity vulnerability in bolo-blog bolo-solo, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1813 exists.

Affected product: bolo-blog bolo-solo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1813/ (Markdown: https://insights.sbomify.com/CVE-2026-1813/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1813
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1813
- OSV: https://osv.dev/vulnerability/CVE-2026-1813

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1813/
Summaries are generated and may contain mistakes; the official description above is the record.