CVE
paopao-ce path traversal enables arbitrary file deletion in LocalOSS
Affects paopao-ce v0.2.0 through v0.6.0-alpha.3 when storage runs on LocalOSS, the default in the official compose file. The checked facts list no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. paopao-ce versions v0.2.0 to v0.6.0-alpha.3 Storage runs on LocalOSS, the default in the official compose file
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Rocboss paopao-ce 0.2.0 through 0.6.0-alpha.3 contains a path traversal vulnerability in LocalOSS DeleteObject that allows authenticated users to delete arbitrary files by submitting crafted media values. Attackers can send dot-dot-slash sequences in the avatar or media content to POST /v1/user/avatar or POST /v1/post/comment, deleting server-writable files including configuration and data.
Who should check
Anyone running paopao-ce v0.2.0 to v0.6.0-alpha.3 with LocalOSS storage, the default in the official compose file.
“Affected versions: v0.2.0 to v0.6.0-alpha.3”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
paopao-ce versions v0.2.0 to v0.6.0-alpha.3 Storage runs on LocalOSS, the default in the official compose fileWorkaround: The checked facts name no workaround. The affected setup is storage on LocalOSS in these versions, so that is the feature the advisory points to.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129870 (Rocboss paopao-ce 0.2.0 through 0.6.0-alpha.3 Path Traversal in LocalOSS File Deletion), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129870 (entry last updated 2026-11-16):
Affected:
- rocboss paopao-ce: from 0.2.0, through 0.6.0-alpha.3
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- paopao-ce versions v0.2.0 to v0.6.0-alpha.3 (source: https://vul.yulun.ac.cn/20261116/paopao-ce/)
- Storage runs on LocalOSS, the default in the official compose file (source: https://vul.yulun.ac.cn/20261116/paopao-ce/)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129870 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129870 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vul.yulun.ac.cn/20261116/paopao-ce/
- https://github.com/rocboss/paopao-ce/blob/v0.6.0-alpha.3/internal/servants/web/core.go#L361-L371
- https://github.com/rocboss/paopao-ce/blob/v0.6.0-alpha.3/internal/dao/storage/localoss.go#L149-L151
- https://github.com/rocboss/paopao-ce
- https://www.vulncheck.com/advisories/rocboss-paopao-ce-0.2.0-through-0.6.0-alpha.3-path-traversal-in-localoss-file-deletion
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129870
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129870"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- rocboss paopao-ce
From 0.2.0 · through 0.6.0-alpha.3
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Repository
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129870
Is CVE-2026-129870 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A logged-in user can delete files on the server, including server-writable configuration and data files.Source: vul.yulun.ac.cn
Which versions are affected by CVE-2026-129870?
paopao-ce: from 0.2.0 through 0.6.0-alpha.3.Source: cve.now feed data
Am I affected, and how do I check?
Versions v0.2.0 through v0.6.0-alpha.3 are affected when storage runs on LocalOSS, which is the default in the official compose file. Check which storage backend your deployment uses to see whether this setup applies.Source: vul.yulun.ac.cn
How do I fix CVE-2026-129870?
The checked facts name no fixed version or vendor patch identifiers, so no upgrade target can be given from them. Check the vendor's advisory for an updated release.Source: vul.yulun.ac.cn
What if there's no patch?
The checked facts name no workaround. The affected setup is storage on LocalOSS in these versions, so that is the feature the advisory points to.Source: vul.yulun.ac.cn