Vulnerability Scan Result

Target:

https://www.cefcu.com/

Scanned target: https://www.cefcu.com/

Submitted: Apr 18, 2026 from HR

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	CEFCU. Not a Bank. Better. — Your Trusted Financial Partner - CEFCU
Description:

IP Information

ip_address	50.227.242.13
country	US
network_name	ARIN
asn	AS22289

Open Ports

443/tcp

https

Apache httpd -

Web Technologies

Software / Version	Category
Google Ads	Advertising
Amazon Web Services	PaaS
Amazon S3	CDN
Linkedin Insight Tag	Analytics
Font Awesome	Font scripts
Bootstrap	UI frameworks
core-js 3.1.3	JavaScript libraries
Google Analytics	Analytics
Apache HTTP Server	Web servers
jQuery 1.11.0	JavaScript libraries
jQuery UI 1.10.4	JavaScript libraries
lit-element 4.1.1	JavaScript libraries
Google Maps	Maps
MySQL	Databases
Open Graph	Miscellaneous
Partytown	Performance
PHP	Programming languages
DoubleClick Floodlight	Advertising
Google Ads Conversion Tracking	Analytics
WordPress	CMS, Blogs
CookieYes	Cookie compliance
DigiCert	SSL/TLS certificate authorities
Google Tag Manager	Tag managers
HSTS	Security
YouTube	Video players

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2021-41184	6.5	0.25367	0.96221	jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.
CVE-2021-41183	6.5	0.02921	0.86415	jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of various `Text` options of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. The values passed to various `Text` options are now always treated as pure text, not HTML. A workaround is to not accept the value of the `*Text` options from untrusted sources.
CVE-2021-41182	6.5	0.24078	0.96075	jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector. A workaround is to not accept the value of the `altField` option from untrusted sources.
CVE-2022-31160	6.1	0.10183	0.93144	jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, someone who can change the initial HTML can wrap all the non-input contents of the `label` in a `span`.
CVE-2016-7103	6.1	0.01397	0.80427	Cross-site scripting (XSS) vulnerability in jQuery UI before 1.12.0 might allow remote attackers to inject arbitrary web script or HTML via the closeText parameter of the dialog function.

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2020-11023	6.9	0.42137	0.97454	In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11022	6.9	0.03538	0.87689	In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2019-11358	6.1	0.02646	0.85759	jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
CVE-2015-9251	6.1	0.27164	0.96396	jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.

Vulnerability description

Risk description

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://www.cefcu.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. default-src: data: URI in default-src allows the execution of unsafe scripts. object-src: We recommend restricting object-src to 'none'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

https://www.cefcu.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. default-src: data: URI in default-src allows the execution of unsafe scripts. object-src: We recommend restricting object-src to 'none'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

CWE	CWE-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Google Ads	Advertising
Amazon Web Services	PaaS
Amazon S3	CDN
Linkedin Insight Tag	Analytics
Font Awesome	Font scripts
Bootstrap	UI frameworks
core-js 3.1.3	JavaScript libraries
Google Analytics	Analytics
Apache HTTP Server	Web servers
jQuery 1.11.0	JavaScript libraries
jQuery UI 1.10.4	JavaScript libraries
lit-element 4.1.1	JavaScript libraries
Google Maps	Maps
MySQL	Databases
Open Graph	Miscellaneous
Partytown	Performance
PHP	Programming languages
DoubleClick Floodlight	Advertising
Google Ads Conversion Tracking	Analytics
WordPress	CMS, Blogs
CookieYes	Cookie compliance
DigiCert	SSL/TLS certificate authorities
Google Tag Manager	Tag managers
HSTS	Security
YouTube	Video players

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://www.cefcu.com/privacy-policy.html	GET	Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36	Email Address: dirrera@cefcu.com

Vulnerability description

We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.

Risk description

The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.

Recommendation

Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://www.cefcu.com/.well-known/security.txt

Vulnerability description

We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.

Risk description

There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.

Recommendation

We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.

Classification

CWE	CWE-1188
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.cefcu.com	A	IPv4 address	50.227.242.13
www.cefcu.com	CNAME	Canonical name	www.gslb2.cefcu.com

Risk description

An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.

Recommendation

We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.

Operating System	Accuracy
OpenBSD 4.0	88%

Evidence

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Google Maps	Maps
YouTube	Video players
Bootstrap	UI frameworks
Amazon Web Services	PaaS
Apache HTTP Server	Web servers
Google Ads	Advertising
jQuery UI	JavaScript libraries
jQuery	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics	Analytics
Google Ads Conversion Tracking	Analytics
CookieYes	Cookie compliance
DoubleClick Floodlight	Advertising
Linkedin Insight Tag	Analytics
HSTS	Security
DigiCert	SSL/TLS certificate authorities
Amazon S3	CDN

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.