Diary-entry deletion via CSRF-unprotected GET request
Published Mar 27, 2026 · Updated Mar 27, 2026
Cross-site request forgery in SourceCodester Diary App 1.0 allows remote attackers to delete diary entries through diary.php. The deletion branch reads the delete query parameter from a GET request and executes a user-scoped DELETE statement without checking a CSRF token or request origin. Exploitation requires an authenticated user with an active session to visit an attacker-controlled webpage, after which the selected diary entry is permanently deleted.
Summary
What happened
Cross-site request forgery in SourceCodester Diary App 1.0 allows remote attackers to delete diary entries through diary.php. The deletion branch reads the delete query parameter from a GET request and executes a user-scoped DELETE statement without checking a CSRF token or request origin. Exploitation requires an authenticated user with an active session to visit an attacker-controlled webpage, after which the selected diary entry is permanently deleted.
The record
- CVE
- CVE-2026-4968
- Published
- Mar 27, 2026
- Updated
- Mar 27, 2026
- Vendor
- Online Computer and Laptop Store Project
- Product
- Diary App
- Classifications
- CWE-352, CWE-862, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2026CVE publishedPublication date reported by the CVE source.
- Mar 27, 2026Record 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=1.0
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
- Diary App CSRF 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