Database data disclosure via spliced organizationCode
Published Jan 21, 2025 · Updated Mar 18, 2025
SQL injection in pearProjectApi 2.8.10 allows remote authenticated users to read database data through a crafted organizationCode value. The selfList method in project.php passes the request value to getMemberProjects, which splices organizationCode directly into an SQL statement before query execution. A valid memberCode and authenticated session are required; the published proof of concept uses an error-based updatexml expression to disclose the database user.
Summary
What happened
SQL injection in pearProjectApi 2.8.10 allows remote authenticated users to read database data through a crafted organizationCode value. The selfList method in project.php passes the request value to getMemberProjects, which splices organizationCode directly into an SQL statement before query execution. A valid memberCode and authenticated session are required; the published proof of concept uses an error-based updatexml expression to disclose the database user.
The record
- CVE
- CVE-2023-27113
- Published
- Jan 21, 2025
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 21, 2025CVE publishedPublication date reported by the CVE source.
- Mar 18, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- GitHub issue 31 HTTP proof of conceptproof of concept · demonstrated
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