Authenticated client-record disclosure via user-controlled object key
Published Oct 27, 2025 · Updated Oct 27, 2025
Authorization bypass in Code Projects Client Details System 1.0 allows remote authenticated users to read other users' client records. Published records identify an insecure direct object reference but do not disclose the affected endpoint, function, key name, or request format. A valid low-privilege account and network access are required; changing a user-controlled record key bypasses object-level authorization and exposes another user's stored client data.
Summary
What happened
Authorization bypass in Code Projects Client Details System 1.0 allows remote authenticated users to read other users' client records. Published records identify an insecure direct object reference but do not disclose the affected endpoint, function, key name, or request format. A valid low-privilege account and network access are required; changing a user-controlled record key bypasses object-level authorization and exposes another user's stored client data.
The record
- CVE
- CVE-2025-12283
- Published
- Oct 27, 2025
- Updated
- Oct 27, 2025
- Vendor
- Code Projects
- Product
- Client Details System
- Classifications
- CWE-639, CWE-285, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 27, 2025CVE publishedPublication date reported by the CVE source.
- Oct 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Client Details System V1.0 Insecure Direct Object Referenceproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo