Vulnerability Scan Result

Target:

http://fidelitybankng.azurewebsites.net/ (redirect)

Scanned target: https://fidelitybankng.azurewebsites.net/

Submitted: Jul 19, 2025 from TT

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

http://fidelitybankng.azurewebsites.net/

Title:	Fidelity Bank Plc - Banking That Suit Your Lifestyle
Description:	Fidelity Bank provides outstanding Online, Personal Banking, SME Banking, Corporate, Investment, Agric and Private Banking Services...

IP Information

ip_address	20.105.224.24
country	NL
network_name	Microsoft Corporation
asn	AS8075

Open Ports

80/tcp	http	- -
443/tcp	https	- -

Web Technologies

Software / Version	Category
cdnjs	CDN
Crocoblock JetElements	WordPress plugins
Elementor 3.30.1	Page builders, WordPress plugins
Hello Elementor 3.4.4	WordPress themes
Facebook Pixel	Analytics
Font Awesome	Font scripts
Bootstrap	UI frameworks
UIKit	UI frameworks
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.39.0	JavaScript libraries
Google Analytics GA4	Analytics
GSAP	JavaScript frameworks
jQuery	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
lit-element 4.1.1	JavaScript libraries
Google Maps	Maps
MySQL	Databases
Netcore Cloud	Customer data platform, Marketing automation
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
Twitter Emoji (Twemoji)	Font scripts
PWA	Miscellaneous
Priority Hints	Performance
WordPress	CMS, Blogs
ThemeIsle Menu Icons	WordPress plugins
ElementsKit	WordPress plugins
Cloudflare	CDN
Google Tag Manager	Tag managers
HSTS	Security
RSS	Miscellaneous
Slider Revolution 6.7.35	Widgets, Photo galleries
Yoast SEO 25.5	SEO, WordPress plugins

Web Application Vulnerabilities

Evidence

Software / Version	Category
cdnjs	CDN
Crocoblock JetElements	WordPress plugins
Elementor 3.30.1	Page builders, WordPress plugins
Hello Elementor 3.4.4	WordPress themes
Facebook Pixel	Analytics
Font Awesome	Font scripts
Bootstrap	UI frameworks
UIKit	UI frameworks
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.39.0	JavaScript libraries
Google Analytics GA4	Analytics
GSAP	JavaScript frameworks
jQuery	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
lit-element 4.1.1	JavaScript libraries
Google Maps	Maps
MySQL	Databases
Netcore Cloud	Customer data platform, Marketing automation
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
Twitter Emoji (Twemoji)	Font scripts
PWA	Miscellaneous
Priority Hints	Performance
WordPress	CMS, Blogs
ThemeIsle Menu Icons	WordPress plugins
ElementsKit	WordPress plugins
Cloudflare	CDN
Google Tag Manager	Tag managers
HSTS	Security
RSS	Miscellaneous
Slider Revolution 6.7.35	Widgets, Photo galleries
Yoast SEO 25.5	SEO, WordPress plugins

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.

Evidence

URL Evidence

URL	Evidence
https://fidelitybankng.azurewebsites.net/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. 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'. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: script-src directive is missing.`

https://fidelitybankng.azurewebsites.net/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. 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'. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: script-src directive is missing.

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-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://fidelitybankng.azurewebsites.net/	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: true.serve@fidelitybank.ng

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://fidelitybankng.azurewebsites.net/.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.

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
fidelitybankng.azurewebsites.net	A	IPv4 address	20.105.224.24
fidelitybankng.azurewebsites.net	CNAME	Canonical name	waws-prod-am2-679.sip.azurewebsites.windows.net

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.

Evidence

Software / Version	Category
WordPress	CMS, Blogs
Slider Revolution 6.7.35	Widgets, Photo galleries
MySQL	Databases
PHP	Programming languages
Google Maps	Maps
Nginx	Web servers, Reverse proxies
UIKit	UI frameworks
Bootstrap	UI frameworks
Yoast SEO Premium 25.5	SEO
HSTS	Security
Hello Elementor 3.4.4	WordPress themes
ThemeIsle Menu Icons	WordPress plugins
Elementor 3.30.1	Page builders, WordPress plugins
Yoast SEO 25.5	SEO, WordPress plugins
Netcore Cloud	Customer data platform, Marketing automation
jQuery Migrate 3.4.1	JavaScript libraries
jQuery	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Font Awesome	Font scripts
Cloudflare	CDN
Priority Hints	Performance
Facebook Pixel	Analytics
cdnjs	CDN
RSS	Miscellaneous
Open Graph	Miscellaneous

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.