Settings modification via missing CSRF check
Published Nov 17, 2021 · Updated Aug 3, 2024
Cross-site request forgery in Dipak Gajjar WP Performance Score Booster before 2.1 allows remote attackers to alter settings via a crafted request. The settings-saving path accepts state-changing requests without a CSRF check, so a request sent through an administrator's active WordPress session is trusted. An attacker must induce a logged-in administrator's browser to submit the request; the demonstrated consequence is modification of plugin configuration.
Summary
What happened
Cross-site request forgery in Dipak Gajjar WP Performance Score Booster before 2.1 allows remote attackers to alter settings via a crafted request. The settings-saving path accepts state-changing requests without a CSRF check, so a request sent through an administrator's active WordPress session is trusted. An attacker must induce a logged-in administrator's browser to submit the request; the demonstrated consequence is modification of plugin configuration.
The record
- CVE
- CVE-2021-24776
- Published
- Nov 17, 2021
- Updated
- Aug 3, 2024
- Vendor
- Dipak Gajjar
- Product
- WP Performance Score Booster
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 17, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=2.1 <2.1
What conditions does exploitation require?
What is affected?
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