Account takeover via unvalidated GET request
Published Jul 14, 2021 · Updated Aug 4, 2024
Cross-site request forgery in Booking Core 1.7.0 allows remote attackers to take over accounts through a crafted GET request. The application accepts state-changing GET requests without validating the CSRF token, letting an attacker replace a logged-in victim's account email address. A victim must visit attacker-controlled content while authenticated; a subsequent password reset is delivered to the substituted address.
Summary
What happened
Cross-site request forgery in Booking Core 1.7.0 allows remote attackers to take over accounts through a crafted GET request. The application accepts state-changing GET requests without validating the CSRF token, letting an attacker replace a logged-in victim's account email address. A victim must visit attacker-controlled content while authenticated; a subsequent password reset is delivered to the substituted address.
The record
- CVE
- CVE-2020-27379
- Published
- Jul 14, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, T1098
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- Booking Core account-email-change CSRF demonstrationproof 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