Unauthorized data changes via undisclosed CSRF locus
Published Jun 14, 2022 · Updated Aug 3, 2024
Cross-site request forgery in PHPGurukul Tourism Management System 3.2 allows remote attackers to alter application data through a victim's session. The public record does not identify the affected request handler or the state-changing operation that lacks CSRF validation. Exploitation requires an authenticated user to interact with attacker-controlled content, and the published impact is limited to low-integrity changes.
Summary
What happened
Cross-site request forgery in PHPGurukul Tourism Management System 3.2 allows remote attackers to alter application data through a victim's session. The public record does not identify the affected request handler or the state-changing operation that lacks CSRF validation. Exploitation requires an authenticated user to interact with attacker-controlled content, and the published impact is limited to low-integrity changes.
The record
- CVE
- CVE-2022-30930
- Published
- Jun 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 2022CVE 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?
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.
Weakness, pattern, technique
Public exploit references
- My Second CVE CVE-2022-30930 proof of conceptproof of concept · unverified
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