VulnerabilityPublished 28 Sep 2025

CVE-2025-11125: langleyfcu Online Banking System · Cross-site Scripting

Affects langleyfcu Online Banking SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% 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 28 Sep 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 26 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.
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 this vulnerability effectively, European organizations should implement strict input validation and sanitization on all user-supplied data, especially parameters reflected in error messages. Employ context-aware output encoding to neutralize any injected scripts before rendering in the browser. Deploy Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. Conduct thorough code reviews and automated security testing focusing on error handling components. Given the rolling release model, establish continuous monitoring of vendor updates and security advisories to apply patches promptly once available. Educate users about phishing risks and encourage cautious behavior when clicking on links, particularly those leading to error pages. Implement multi-factor authentication (MFA) to reduce the impact of credential theft. Finally, consider web application firewalls (WAFs) with XSS detection rules as an additional layer of defense.

Description

A vulnerability was found in langleyfcu Online Banking System up to 57437e6400ce0ae240e692c24e6346b8d0c17d7a. Affected by this vulnerability is an unknown functionality of the file /connection_error.php of the component Error Message Handler. Performing manipulation of the argument Error results in cross site scripting. Remote exploitation of the attack is possible. The exploit has been made public and could be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided.

Impact

For European organizations, particularly financial institutions using the langleyfcu Online Banking System, this XSS vulnerability poses significant risks. Exploitation could lead to unauthorized access to user sessions, theft of sensitive personal and financial data, and fraudulent transactions, undermining customer trust and potentially causing financial losses. Regulatory bodies such as the European Banking Authority (EBA) and GDPR enforcement agencies may impose penalties for inadequate security controls. The reputational damage from a successful attack could be severe, affecting customer retention and market position. Additionally, the rolling release model may delay timely patching, increasing exposure. The medium severity rating suggests a moderate but tangible threat that requires prompt attention to prevent exploitation, especially as phishing and social engineering attacks remain prevalent in Europe. Organizations may also face increased scrutiny from regulators demanding evidence of proactive vulnerability management and incident response readiness.

Summary

CVE-2025-11125 identifies a cross-site scripting (XSS) vulnerability in the langleyfcu Online Banking System, affecting the error message handler component within the /connection_error.php file. The vulnerability arises from improper sanitization of the 'Error' parameter, allowing attackers to inject arbitrary JavaScript code that executes in the context of the victim's browser. This flaw can be exploited remotely without authentication, though it requires user interaction, such as clicking a crafted link or visiting a malicious webpage that triggers the vulnerable error handler. The product uses a rolling release approach, complicating version tracking and patch management, and no explicit patch link is provided. The CVSS 4.0 score of 5.3 reflects medium severity, considering the network attack vector, low complexity, no privileges required, but requiring user interaction and resulting in limited integrity impact. Potential attack vectors include phishing campaigns that redirect users to URLs with malicious payloads in the error parameter, leading to session hijacking, theft of sensitive banking credentials, or unauthorized transactions. Although no known exploits are currently active in the wild, the public disclosure of exploit code increases the likelihood of future attacks. The vulnerability highlights the need for secure coding practices, especially in online banking platforms where trust and data confidentiality are paramount.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 6 Oct 2025, 00:45 UTC

Technical details

References

Community reviews

Related threats