CVE-2025-70899VulnerabilityPublished 22 Jan 2026Updated 23 Jan 2026

CVE-2025-70899: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 08:11 UTC

CVSS 3.1 base score

6.5Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

AI-suggested

To mitigate CVE-2025-70899, organizations should implement robust CSRF protection mechanisms on all administrative forms within PHPgurukul Online Course Registration v3.1. This includes generating unique CSRF tokens for each user session and validating these tokens on the server side for every state-changing request. Developers should ensure that all forms and AJAX requests that perform administrative actions include these tokens. Additionally, administrators should be trained to recognize phishing attempts and avoid clicking on suspicious links or visiting untrusted websites while logged into administrative accounts. Network-level protections such as Web Application Firewalls (WAFs) can be configured to detect and block suspicious CSRF attack patterns. Organizations should monitor administrative actions for anomalies that could indicate exploitation attempts. Since no official patches are currently available, organizations may consider applying custom patches or workarounds to introduce CSRF tokens or restrict administrative access to trusted networks or VPNs. Regular security assessments and penetration testing focused on CSRF and related web vulnerabilities are recommended to ensure ongoing protection.

Description

CVE-2025-70899 is a medium-severity vulnerability in PHPgurukul Online Course Registration v3.1 caused by the absence of Cross-Site Request Forgery (CSRF) protection on all administrative forms. This flaw allows attackers to trick authenticated administrators into performing unauthorized actions by visiting malicious web pages, potentially leading to integrity compromise of administrative functions. The vulnerability requires user interaction but no prior authentication or privileges by the attacker. Although no known exploits are reported in the wild, the vulnerability poses a significant risk to the integrity of affected systems. The CVSS score is 6.5, reflecting the ease of exploitation and impact on integrity without affecting confidentiality or availability. European organizations using this software, especially educational institutions, are at risk of unauthorized administrative changes. Mitigation requires implementing CSRF tokens and validating them on all administrative forms, alongside user education to avoid malicious links. Countries with higher adoption of PHPgurukul or similar educational platforms, such as Germany, France, and the UK, are more likely to be affected.

Impact

For European organizations, particularly educational institutions using PHPgurukul Online Course Registration v3.1, this vulnerability poses a risk of unauthorized administrative actions that can alter course registrations, user permissions, or other critical administrative settings. Such unauthorized changes can disrupt operations, lead to data integrity issues, and potentially facilitate further attacks if administrative privileges are escalated or misused. While confidentiality and availability are not directly impacted, the integrity compromise can undermine trust in the system and cause operational disruptions. The requirement for user interaction limits the attack surface but does not eliminate risk, especially if administrators are targeted via phishing or social engineering campaigns. The absence of known exploits suggests limited current exploitation, but the vulnerability’s nature makes it a likely target once exploit code becomes available. European organizations with limited security awareness or lacking web application protections are particularly vulnerable. The impact is more pronounced in countries with higher adoption of PHPgurukul or similar platforms in educational sectors.

Summary

The vulnerability identified as CVE-2025-70899 affects PHPgurukul Online Course Registration version 3.1. It stems from a lack of Cross-Site Request Forgery (CSRF) protection on all administrative forms within the application. CSRF is a web security issue where unauthorized commands are transmitted from a user that the web application trusts. In this case, an attacker can craft a malicious webpage that, when visited by an authenticated administrator, causes the administrator’s browser to submit unauthorized requests to the vulnerable application. These requests can perform administrative actions without the administrator’s consent or knowledge, compromising the integrity of the system’s administrative functions. The vulnerability does not require the attacker to have any privileges or prior authentication, but it does require the victim administrator to interact with a malicious webpage (user interaction). The CVSS v3.1 score of 6.5 reflects a medium severity, with the vector indicating network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. No known exploits have been reported in the wild, and no patches or fixes are currently linked. The CWE identifier CWE-352 confirms the nature of the vulnerability as CSRF. The vulnerability was reserved and published in January 2026, indicating it is a recent discovery. The lack of CSRF tokens or equivalent anti-CSRF mechanisms on administrative forms is the root cause, making it possible for attackers to perform unauthorized state-changing operations on behalf of legitimate administrators.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Jan 2026, 10:14 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats