VulnerabilityPublished 27 Mar 2026

CVE-2026-4968: SourceCodester Diary App · Cross-Site Request Forgery

Affects SourceCodester Diary AppSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SourceCodesterDiary App	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-4968, organizations and users should implement robust CSRF protections, including the use of anti-CSRF tokens in all state-changing requests within the Diary App. Developers should ensure that all forms and state-changing endpoints validate these tokens server-side. Additionally, implementing SameSite cookie attributes can reduce CSRF risks by restricting cookie transmission. User education is critical to reduce the likelihood of clicking malicious links or visiting untrusted websites. Network-level protections such as web application firewalls (WAFs) can be configured to detect and block suspicious CSRF attack patterns. Until an official patch is released, consider restricting access to the Diary App to trusted networks or users and monitoring logs for unusual activity. Regularly updating the app and applying security best practices for session management and input validation will further reduce risk.

Description

A vulnerability was determined in SourceCodester Diary App 1.0. The affected element is an unknown function of the file diary.php. Executing a manipulation can lead to cross-site request forgery. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.

Impact

The primary impact of CVE-2026-4968 is the potential for unauthorized actions within the Diary App, which could include modifying, deleting, or adding diary entries or other user data. Since the vulnerability requires user interaction but no authentication, attackers can target users through phishing or malicious websites to exploit the flaw. This can lead to data integrity issues and potential user trust erosion. Confidentiality and availability impacts are minimal or nonexistent. For organizations, especially those relying on this app for personal or sensitive diary management, the risk includes unauthorized data manipulation and potential privacy concerns if diary entries are sensitive. The lack of patches and public exploit code increases the urgency for mitigation. While the vulnerability is medium severity, its exploitation could facilitate further attacks if combined with other vulnerabilities or social engineering tactics.

Summary

CVE-2026-4968 identifies a Cross-Site Request Forgery (CSRF) vulnerability in SourceCodester Diary App version 1.0, located in an unspecified function within the diary.php file. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a forged request to a web application, causing the application to perform unintended actions on behalf of the user. This vulnerability is remotely exploitable without requiring prior authentication, but it does require user interaction, such as clicking a crafted link or visiting a malicious webpage. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:P), no impact on confidentiality (VC:N), low impact on integrity (VI:L), and no impact on availability (VA:N). The vulnerability does not involve scope or security requirements changes. Although no known exploits are currently active in the wild and no official patches have been released, the public disclosure of this vulnerability increases the risk of exploitation. The lack of specific details about the vulnerable function limits precise technical mitigation but confirms the need for standard CSRF defenses. The vulnerability primarily threatens the integrity of user data and application state by enabling unauthorized actions to be performed without user consent.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 18:11 UTC

Technical details

References

Community reviews

Related threats