CVE-2026-129143 in paicodinginfo

Summary

by MITRE • 11/13/2026

paicoding 1.0.3 contains a missing authorization vulnerability in the ArticleRestController article detail endpoint that allows unauthenticated attackers to read restricted articles. Attackers can enumerate article IDs via GET /article/api/data/detail/{articleId} to retrieve full content of paid, login-only, member-only and draft articles.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/13/2026

The security flaw identified in paicoding version 1.0.3 represents a critical failure in access control mechanisms within the ArticleRestController component. Specifically, the vulnerability resides in the endpoint designed for retrieving article details via the GET /article/api/data/detail/{articleId} route. This function is intended to serve as the primary interface for delivering content to authorized users who have purchased or subscribed to specific articles. However, due to a missing authorization check, this endpoint does not validate whether the requesting user possesses the necessary permissions or has completed the required authentication and payment processes before releasing sensitive data. Consequently, any individual with network access to the application can invoke this API without providing valid session tokens, credentials, or proof of purchase, effectively bypassing all intended security boundaries designed to protect proprietary content.

From a technical perspective, this vulnerability is classified as an Insecure Direct Object Reference (IDOR), which aligns with CWE-639 in the Common Weakness Enumeration standard. The root cause lies in the application's reliance on the article identifier provided by the client within the URL path without cross-referencing it against the user’s permission context or ownership records. Because modern web applications often use sequential integer-based identifiers for database entities, attackers can easily perform enumeration attacks to iterate through a range of article IDs. By systematically requesting details for different ID values, an attacker can harvest a comprehensive list of available articles along with their full textual content, metadata, and potentially associated user information if such data is exposed in the response payload. This behavior exemplifies CWE-284, Improper Access Control, where the system fails to enforce proper authorization checks on sensitive resources.

The operational impact of this vulnerability is severe for both the service provider and its legitimate users. For content creators and publishers using paicoding, the exposure leads directly to intellectual property theft and revenue loss, as paid or subscription-based material becomes freely accessible to unauthorized parties. This undermines the core business model that relies on exclusive access to high-quality articles. Furthermore, if draft articles are also exposed, it may result in premature disclosure of unpublished work, causing reputational damage and potential legal complications regarding confidentiality agreements with contributors. For end-users, while their personal data might not be directly compromised by this specific vector unless linked profiles are involved, the erosion of trust in the platform's ability to protect paid content can lead to churn and loss of customer confidence. The vulnerability also facilitates broader reconnaissance activities, as the successful enumeration of article IDs provides attackers with a map of the application’s content structure and potentially reveals patterns that could aid in further exploitation attempts against other parts of the system.

To mitigate this risk, immediate remediation efforts should focus on implementing robust server-side authorization checks within the ArticleRestController method handling the detail endpoint. The application must verify that the authenticated user associated with the current session has explicit permission to view the specific article identified by the requested ID. This involves querying the database or access control list to confirm a relationship between the user’s account and the resource before returning any data. Additionally, developers should consider implementing rate limiting on API endpoints to slow down enumeration attempts and adding logging mechanisms to detect abnormal patterns of requests that may indicate automated scanning activity. From an architectural standpoint, adopting principles such as least privilege ensures that users only access resources they are explicitly granted permission to view. Regular security audits and penetration testing focusing on broken object level authorization will help prevent similar vulnerabilities in future releases. Aligning these fixes with the MITRE ATT&CK framework’s T1078 (Valid Accounts) or T1592 (Gather Victim Host Information) tactics can guide more comprehensive defense strategies against such exploitation techniques.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00286

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!