Author-level settings access expansion via capability manipulation
Published Apr 29, 2024 · Updated Aug 1, 2024
Broken access control in SWEET CODE CHEF SL GamiPress before 6.8.9 allows remote authenticated users to modify plugin settings. The published proof of concept varies the role-capability value used by the settings access-control mechanism, which fails to enforce the configured minimum role. An Author account and a crafted request are required; exploitation permits unauthorized configuration changes and can extend settings access to Subscribers.
Summary
What happened
Broken access control in SWEET CODE CHEF SL GamiPress before 6.8.9 allows remote authenticated users to modify plugin settings. The published proof of concept varies the role-capability value used by the settings access-control mechanism, which fails to enforce the configured minimum role. An Author account and a crafted request are required; exploitation permits unauthorized configuration changes and can extend settings access to Subscribers.
The record
- CVE
- CVE-2024-2505
- Published
- Apr 29, 2024
- Updated
- Aug 1, 2024
- Vendor
- SWEET CODE CHEF SL
- Product
- GamiPress
- Classifications
- CWE-284, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record 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=0 <6.8.9
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
- WPScan role-capability 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