Vulnerability Scan Result

Target:

https://www.lloydsbanktrade.com/ (redirect)

Scanned target: https://www.lloydsbanktrade.com/en

Submitted: Nov 18, 2025 from SC

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Home - International Trade Portal
Description:	Your source for import / export opportunities worldwide

IP Information

ip_address	51.68.243.42
country	FR
network_name	OVH SAS
asn	AS16276

Open Ports

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

Web Technologies

Software / Version	Category
Microsoft Advertising	Advertising
cdnjs	CDN
Crazy Egg	Analytics
Adobe Experience Platform Identity Service	Customer data platform
Bootstrap 5-3-3	UI frameworks
web-vitals	JavaScript libraries, RUM
jQuery Migrate 1.4.1	JavaScript libraries
SWFObject	Miscellaneous
jQuery	JavaScript libraries
jQuery UI	JavaScript libraries
Popper	Miscellaneous
script.aculo.us	JavaScript libraries
Tealium	Tag managers, Customer data platform
Adobe Analytics	Analytics
DreamWeaver	Editors
Cloudflare	CDN
CrownPeak	CMS, Miscellaneous
DigiCert	SSL/TLS certificate authorities
LivePerson	Live chat
Prototype	JavaScript frameworks
Qualtrics	Surveys
HSTS	Security
ServiceNow	Miscellaneous

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.lloydsbanktrade.com/en	SFSESSID	Set-Cookie: SFSESSID=2lrsdcoqm3gc6bh5tdmpj8g8r0

Vulnerability description

We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

Classification

CWE	CWE-614
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://www.lloydsbanktrade.com/en	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: data: URI in default-src allows the execution of unsafe scripts. 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'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). object-src: We recommend restricting object-src to 'none'.

https://www.lloydsbanktrade.com/en

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: data: URI in default-src allows the execution of unsafe scripts. 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'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). object-src: We recommend restricting object-src to 'none'.

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

Software / Version	Category
Microsoft Advertising	Advertising
cdnjs	CDN
Crazy Egg	Analytics
Adobe Experience Platform Identity Service	Customer data platform
Bootstrap 5-3-3	UI frameworks
web-vitals	JavaScript libraries, RUM
jQuery Migrate 1.4.1	JavaScript libraries
SWFObject	Miscellaneous
jQuery	JavaScript libraries
jQuery UI	JavaScript libraries
Popper	Miscellaneous
script.aculo.us	JavaScript libraries
Tealium	Tag managers, Customer data platform
Adobe Analytics	Analytics
DreamWeaver	Editors
Cloudflare	CDN
CrownPeak	CMS, Miscellaneous
DigiCert	SSL/TLS certificate authorities
LivePerson	Live chat
Prototype	JavaScript frameworks
Qualtrics	Surveys
HSTS	Security
ServiceNow	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.

Evidence

URL
https://www.lloydsbanktrade.com/robots.txt

Vulnerability description

We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.

Risk description

There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.

Recommendation

We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).

Evidence

URL
Missing: https://www.lloydsbanktrade.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.

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.lloydsbanktrade.com	A	IPv4 address	51.68.243.42
www.lloydsbanktrade.com	CNAME	Canonical name	lloydsbanktrade.export-entreprises.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.

Evidence

Software / Version	Category
DreamWeaver	Editors
Bootstrap 5-3-3	UI frameworks
Tealium	Tag managers, Customer data platform
Prototype	JavaScript frameworks
Cloudflare	CDN
script.aculo.us	JavaScript libraries
Qualtrics	Surveys
LivePerson	Live chat
jQuery UI	JavaScript libraries
jQuery Migrate 1.4.1	JavaScript libraries
jQuery	JavaScript libraries
cdnjs	CDN
Crazy Egg	Analytics
web-vitals	JavaScript libraries, RUM
HSTS	Security
DigiCert	SSL/TLS certificate authorities
SWFObject	Miscellaneous
CrownPeak	CMS, 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.