CVE-2025-13119VulnerabilityPublished 13 Nov 2025

CVE-2025-13119: Fabian Ros Simple E-Banking System · Cross-Site Request Forgery

Affects Fabian Ros Simple E-Banking SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 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 16% 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 13 Nov 2025
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-25.

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

Affected software

Product	Affected	Fixed in
Fabian Ros Simple E-Banking System	Affected =1.0	Fixed in–

AI-suggested

1. Implement anti-CSRF tokens in all state-changing requests to ensure that requests originate from legitimate users. 2. Validate the HTTP Referer and Origin headers on the server side to confirm requests come from trusted sources. 3. Enforce SameSite cookie attributes to restrict cross-origin requests. 4. Educate users about the risks of clicking on suspicious links or visiting untrusted websites, as user interaction is required for exploitation. 5. Monitor transaction logs for unusual activities that may indicate exploitation attempts. 6. If possible, upgrade or patch the Simple E-Banking System once an official fix is released. 7. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block CSRF attack patterns. 8. Conduct regular security assessments and penetration testing focused on CSRF and related web vulnerabilities. 9. Limit session lifetimes and enforce multi-factor authentication to reduce the window of opportunity for attackers. 10. Collaborate with vendors and security communities to stay informed about updates and emerging threats related to this vulnerability.

Description

CVE-2025-13119 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability affecting Fabian Ros Simple E-Banking System version 1.0. The flaw allows remote attackers to trick authenticated users into executing unwanted actions without their consent, potentially altering banking operations. Exploitation requires user interaction but no authentication or privileges beyond those of the victim. Although no known exploits are currently in the wild, a proof-of-concept has been published, increasing the risk of future attacks. The vulnerability impacts the integrity and potentially the availability of banking transactions but does not directly compromise confidentiality. European organizations using this e-banking system should prioritize mitigation to prevent unauthorized transaction manipulation. Countries with higher adoption of this software or significant banking sectors are at greater risk. Immediate mitigation includes implementing anti-CSRF tokens, validating request origins, and educating users about phishing risks. Given the medium CVSS score of 5.

Impact

For European organizations, this vulnerability poses a risk of unauthorized manipulation of banking transactions, potentially leading to financial losses, fraud, and erosion of customer trust. While the vulnerability does not directly expose confidential data, unauthorized transaction changes can disrupt financial operations and cause reputational damage. Banks and financial institutions using the affected Simple E-Banking System version 1.0 are particularly vulnerable. The attack vector requires user interaction, so phishing or social engineering campaigns could be used to exploit this flaw. The impact is more pronounced in countries with higher adoption of this software or where smaller banks and financial institutions rely on this system. Regulatory compliance frameworks in Europe, such as GDPR and PSD2, may impose additional obligations to address such vulnerabilities promptly. Failure to mitigate could result in regulatory penalties and loss of customer confidence.

Summary

CVE-2025-13119 identifies a Cross-Site Request Forgery (CSRF) vulnerability in Fabian Ros Simple E-Banking System version 1.0. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a forged HTTP request, causing the user’s browser to perform unwanted actions on a web application where they are logged in. In this case, the vulnerability allows remote attackers to initiate banking operations without the user's consent or knowledge. The vulnerability does not require the attacker to have any privileges or authentication, but it does require the victim to interact with a malicious link or webpage (user interaction). The CVSS 4.0 vector indicates the attack is network-based (AV:N), requires low attack complexity (AC:L), no privileges (PR:N), no authentication (AT:N), but requires user interaction (UI:P). The impact primarily affects the integrity of banking transactions (VI:L) with no direct confidentiality or availability impact. The exploit code has been published, which raises the likelihood of exploitation attempts. Given the sensitive nature of e-banking systems, even a medium severity vulnerability can have significant consequences if exploited.

References

Community reviews

Loading reviews…