CVE
paopao-ce wallet balance minting via negative attachment price
Affects paopao-ce through 0.6.0-alpha.3, where post creation accepts charge attachments with an unvalidated attachment_price. No fixed version is listed.
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:N/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. Affects paopao-ce through 0.6.0-alpha.3 Post creation accepts charge attachments with an unvalidated attachment_price
- 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
Summary
Rocboss paopao-ce through 0.6.0-alpha.3 fails to validate the attachment_price field when creating posts, allowing authenticated users to set negative prices on charge attachments. Attackers with two ordinary accounts can download the attachment via GET /v1/attachment, where the negative price increases the buyer's wallet balance, minting funds to purchase other users' paid attachments.
Who should check
Teams running paopao-ce through 0.6.0-alpha.3 that sell paid (charge) attachments
“Affecting paopao-ce <= 0.6.0-alpha.3”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- 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.
Affects paopao-ce through 0.6.0-alpha.3 Post creation accepts charge attachments with an unvalidated attachment_priceWorkaround: The checked facts include no workaround or vendor guidance for the period before a fix.
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-129868 (Rocboss paopao-ce through 0.6.0-alpha.3 Wallet Balance Minting via Negative Attachment Price), 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-129868 (entry last updated 2026-11-16):
Affected:
- rocboss paopao-ce: through 0.6.0-alpha.3
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects paopao-ce through 0.6.0-alpha.3 (source: https://www.vulncheck.com/advisories/rocboss-paopao-ce-through-0.6.0-alpha.3-wallet-balance-minting-via-negative-attachment-price)
- Post creation accepts charge attachments with an unvalidated attachment_price (source: https://www.vulncheck.com/advisories/rocboss-paopao-ce-through-0.6.0-alpha.3-wallet-balance-minting-via-negative-attachment-price)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129868 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129868 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/priv.go#L890-L900
- https://github.com/rocboss/paopao-ce/blob/v0.6.0-alpha.3/internal/dao/jinzhu/wallet.go#L101-L117
- https://github.com/rocboss/paopao-ce
- https://www.vulncheck.com/advisories/rocboss-paopao-ce-through-0.6.0-alpha.3-wallet-balance-minting-via-negative-attachment-price
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-129868
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-129868"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- rocboss paopao-ce
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-129868
Is CVE-2026-129868 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 negative attachment_price on post creation increases the buyer's wallet balance, letting an attacker mint funds to buy other users' paid attachments.Source: vulncheck.com
Which versions are affected by CVE-2026-129868?
paopao-ce: through 0.6.0-alpha.3.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are paopao-ce through 0.6.0-alpha.3, in setups where post creation accepts charge attachments. Readers can compare their installed paopao-ce version with 0.6.0-alpha.3 and check whether their posts use charge attachments.Source: vulncheck.com
How do I fix CVE-2026-129868?
The checked facts name no fixed version and no vendor patch ids, so no upgrade target can be given from them.Source: vulncheck.com
What if there's no patch?
The checked facts include no workaround or vendor guidance for the period before a fix.Source: vulncheck.com