Skip to main content

paopao-ce EUVDEUVD-2026-103071

| CVE-2026-111649 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-16 VulnCheck GHSA-x97c-6hxr-5qp6
7.1
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged user
  2. Exploit
    Enumerate sequential post_content IDs
  3. Execution
    Request signed URL via /v1/attachment endpoint
  4. Impact
    Download other users' private media

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Requires a valid authenticated account on the target paopao-ce instance (CVSS PR:L); any ordinary registered low-privileged user suffices, with no admin role needed. The DownloadAttachment handler for the /v1/attachment endpoint does not verify that the requesting user owns or is authorized to view the referenced post_content ID, so supplying arbitrary IDs returns signed download URLs for other users' private, friend-only, and following-only media. Exploitation is amplified because content IDs are sequential, enabling trivial enumeration. Limiting factors: an authenticated session is mandatory (not anonymous/unauthenticated), impact is confined to confidentiality of attachments (no write/modify or denial of service), and the issue is present in builds through 0.6.0-alpha.3 under default configuration.

Impact

This is a genuine but bounded data-confidentiality issue rather than a critical infrastructure threat. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) describes a network-reachable, low-complexity attack that requires an authenticated low-privileged account and yields high confidentiality impact with no integrity or availability impact - consistent with a CWE-639 insecure direct object reference. The reported 7.1 score aligns with that profile: serious for the data exposed, but gated by the need for a valid account and limited to reading other users' private media. No EPSS score, CISA KEV entry, or SSVC decision data was provided, so automatable-exploitation and active-exploitation signals cannot be assessed from the input. There is no indication of active exploitation; however, a detailed public technical write-up (hackmd) and a direct link to the vulnerable source (priv.go L208-250) substantially lower the barrier to reproduction. Signals are mutually consistent (no conflict between the CVSS vector and the description), and the primary risk amplifier is that IDs are sequential, making enumeration trivial for any registered user. Missing data to note explicitly: EPSS/KEV/SSVC are absent, so prioritization beyond the CVSS/technical-write-up evidence cannot be quantified.

Exploit ScenarioDerived

An attacker registers or uses any ordinary authenticated account on a paopao-ce instance, then scripts requests to the /v1/attachment endpoint supplying sequential post_content IDs. The server returns signed download URLs for content it does not own, letting the attacker harvest other users' private, friend-only, and following-only images, videos, and attachments. A detailed public write-up describing this enumeration exists, and the low attack complexity (AC:L) means no special timing or conditions are needed beyond holding a valid session.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 16, 2026

Authenticated users of Rocboss paopao-ce through 0.6.0-alpha.3 can obtain signed download URLs for other users' private, friend-only, and following-only media by requesting arbitrary content IDs from the /v1/attachment endpoint. Because post_content IDs are sequential, an ordinary registered low-privileged account (no administrative role required) is enough to enumerate IDs and harvest images, videos, and attachments belonging to other users, giving a high confidentiality impact with no write or availability effect. This is a genuine but bounded data-confidentiality issue rather than a critical infrastructure threat; no public exploit code was identified at time of analysis, although a public technical write-up describing the cross-user IDOR is referenced.

RemediationAI

No vendor-released patch identified at time of analysis; the published references point only to the vulnerable handler source at blob/v0.6.0-alpha.3/internal/servants/web/priv.go#L208-L250 and to project and advisory pages, so an exact fixed version cannot be cited and must be confirmed against the upstream repository before relying on it. Until a fix is available, the most effective mitigation is to add a server-side object-level authorization check in DownloadAttachment that resolves the supplied post_content ID to its owning post and enforces the item's visibility rules (private, friend-only, following-only) against the authenticated session before any signed URL is generated; because the IDs are sequential, this check - not obscurity - is what closes the issue. Secondary compensating controls include replacing sequential post_content identifiers with unguessable values in the API surface, shortening signed-URL time-to-live so leaked links expire quickly (trade-off: shorter validity can break legitimate long-running downloads), and applying rate limiting plus logging/alerting on /v1/attachment enumeration patterns (trade-off: may throttle legitimate heavy clients), or restricting /v1/attachment to trusted networks where it is not needed publicly (trade-off: breaks external media access for legitimate users). Organizations that cannot modify the handler should consider disabling or reverse-proxy blocking the /v1/attachment endpoint entirely, accepting the resulting loss of attachment-download functionality for all users.

Affected VersionsENISA

paopao-ce 0 ≤0.6.0-alpha.3

Affected Packages

euvd paopao_ce no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

paopao-ce is an open-source, Go-based social networking application (rocboss/paopao-ce) whose web service layer is organized under internal/servants/web, with the affected handler code in priv.go lines 208-250. The flaw is CWE-639 (Authorization Bypass Through User-Controlled Key): the DownloadAttachment handler for the /v1/attachment endpoint accepts a client-supplied post_content identifier and generates a signed download URL for the underlying object without verifying that the requesting user owns the content or is permitted to view it under the item's visibility setting (private, friend-only, or following-only). The ID space is sequential, so the authorization decision is effectively delegated to an attacker-controlled, guessable key rather than to a server-side ownership/visibility check. The CPE cpe:2.3:a:rocboss:paopao-ce:*:*:*:*:*:*:*:* indicates the record does not constrain to a fixed version, consistent with the advisory statement that builds through 0.6.0-alpha.3 under default configuration are affected. The independent assessment maps this to CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, i.e. a network-reachable, low-complexity, authenticated confidentiality-only issue with no integrity or availability impact.

Know when Paopao Ce gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 7.1 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Network-reachable endpoint with low complexity, but an authenticated low-privileged account is required (PR:L); impact is confidentiality-only (C:H, I:N, A:N) as the flaw only discloses private media.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Rocboss paopao-ce through 0.6.0-alpha.3 contains an insecure direct object reference vulnerability in DownloadAttachment that allows authenticated users to access private media by supplying arbitrary content IDs. Attackers can enumerate sequential post_content ids via the /v1/attachment endpoint to obtain signed download URLs for other users' private, friend-only and following-only images, videos and attachments.

Executive ViewAI

Why It Matters

Rocboss paopao-ce through 0.6.0-alpha.3 has a high-severity access-control flaw that lets a low-privileged user obtain signed download URLs for other users' private, friend-only, and following-only media, creating a broad confidentiality exposure across user content. No public exploit identified at time of analysis, but a public technical write-up describes the cross-user IDOR, so the issue is discoverable and likely to be replicated. Leadership should care because this can erode user trust, trigger privacy or regulatory scrutiny, and require costly incident response and notification if media is harvested at scale.

Business Impact: High
Compensating Controls

Interim mitigations: restrict access to the /v1/attachment endpoint, enforce server-side ownership and permission checks for requested content IDs, replace sequential post_content IDs with unguessable identifiers, monitor for enumeration patterns, and rotate signing keys if exposure is suspected.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Prevalence
Low
niche open-source Go microblog platform, pre-release alpha, no enterprise footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy