Field-definition changes via missing authorization checks
Published Dec 18, 2023 · Updated Apr 28, 2026
Missing authorization in Participants Database 2.5.5 and earlier allows remote authenticated users to alter database field definitions. Several Manage Database Fields handlers process admin-post requests without enforcing the capability required for field administration. Subscriber-level access is sufficient for direct changes; the CSRF scenario instead requires a privileged user to submit an attacker-controlled request.
Summary
What happened
Missing authorization in Participants Database 2.5.5 and earlier allows remote authenticated users to alter database field definitions. Several Manage Database Fields handlers process admin-post requests without enforcing the capability required for field administration. Subscriber-level access is sufficient for direct changes; the CSRF scenario instead requires a privileged user to submit an attacker-controlled request.
The record
- CVE
- CVE-2023-48751
- Published
- Dec 18, 2023
- Updated
- Apr 28, 2026
- Vendor
- Roland Barker, xnau webdesign
- Product
- Participants Database
- Classifications
- CWE-862, CWE-352, CAPEC-62, CAPEC-1, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 18, 2023CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record 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=n/a <=2.5.5 changes=[{"at":"2.5.6","status":"unaffected"}]
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
No public exploit references are available in this record.
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