Vulnerability Scan Result

Target:

https://www.stewartsandlloyds.co.za/

Scanned target: https://www.stewartsandlloyds.co.za/

Submitted: Mar 22, 2026 from ES

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Stewarts and Lloyds Is A Leading Steel Supplier In South Africa
Description:	Stewarts and Lloyds is a leading supplier of quality steel and tube products, pipes, fittings, valves, pumps, irrigation, fencing, & more.

IP Information

ip_address	172.67.166.225
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	104.21.16.68
country	-
network_name	Cloudflare, Inc.
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	http	cloudflare -

Web Technologies

Software / Version	Category
Magnific Popup 4.0.3	JavaScript libraries
Elementor 3.35.7	Page builders, WordPress plugins
Elfsight	Widgets
Facebook Pixel 2.9.281	Analytics
Flickity	JavaScript libraries
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.46.0	JavaScript libraries
Google Analytics	Analytics
Google Font API	Font scripts
GSAP	JavaScript frameworks
HTTP/3	Miscellaneous
imagesLoaded 5.0.0	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
Lightbox	JavaScript libraries
MySQL	Databases
OceanWP 4.0.3	WordPress themes
Open Graph	Miscellaneous
PHP	Programming languages
Swiper	JavaScript libraries
WordPress	CMS, Blogs
Cloudflare	CDN
Google Tag Manager	Tag managers
RSS	Miscellaneous
SiteGround	PaaS, Hosting
Slider Revolution 6.7.40	Widgets, Photo galleries
YouTube	Video players
Yoast SEO 27.1.1	SEO, WordPress plugins

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2025-8944	4.3	0.00038	0.11456	The OceanWP WordPress theme before 4.1.2 is vulnerable to an option update due to a missing capability check on one of its AJAX request handler, allowing any authenticated users, such as subscriber to update the darkMod` setting.

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

URL	Evidence
https://www.stewartsandlloyds.co.za/wp-content/themes/	Response headers do not include the X-Content-Type-Options HTTP security header

Vulnerability description

We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.

Risk description

The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.

Recommendation

We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://www.stewartsandlloyds.co.za/	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

Risk description

The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).

Recommendation

The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://www.stewartsandlloyds.co.za/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

Software / Version	Category
Magnific Popup 4.0.3	JavaScript libraries
Elementor 3.35.7	Page builders, WordPress plugins
Elfsight	Widgets
Facebook Pixel 2.9.281	Analytics
Flickity	JavaScript libraries
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.46.0	JavaScript libraries
Google Analytics	Analytics
Google Font API	Font scripts
GSAP	JavaScript frameworks
HTTP/3	Miscellaneous
imagesLoaded 5.0.0	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
Lightbox	JavaScript libraries
MySQL	Databases
OceanWP 4.0.3	WordPress themes
Open Graph	Miscellaneous
PHP	Programming languages
Swiper	JavaScript libraries
WordPress	CMS, Blogs
Cloudflare	CDN
Google Tag Manager	Tag managers
RSS	Miscellaneous
SiteGround	PaaS, Hosting
Slider Revolution 6.7.40	Widgets, Photo galleries
YouTube	Video players
Yoast SEO 27.1.1	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.

Classification

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

Evidence

URL	Evidence
https://www.stewartsandlloyds.co.za/	Response does not include the HTTP Content-Security-Policy security header or meta tag

Vulnerability description

We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.

Risk description

The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.

Recommendation

Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.

Classification

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

Evidence

URL	Evidence
https://www.stewartsandlloyds.co.za/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

Vulnerability description

We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.

Risk description

The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.

Recommendation

The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://www.stewartsandlloyds.co.za/.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

Evidence

URL	Method	Parameters	Evidence
https://www.stewartsandlloyds.co.za/wp-json/oembed/1.0/embed	GET	Query: format=xml url=https://www.stewartsandlloyds.co.za/ 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	Possible API endpoint found at `/wp-json/oembed/1.0/embed`

Vulnerability description

We found API endpoints while crawling the given web application.

Risk description

These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.

Recommendation

Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Cloudflare	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.

Evidence

Software / Version	Category
Cloudflare	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.

Evidence

Domain Queried	DNS Record Type	Description	Value
www.stewartsandlloyds.co.za	A	IPv4 address	172.67.166.225
www.stewartsandlloyds.co.za	A	IPv4 address	104.21.16.68
www.stewartsandlloyds.co.za	AAAA	IPv6 address	2606:4700:3035::ac43:a6e1
www.stewartsandlloyds.co.za	AAAA	IPv6 address	2606:4700:3035::6815:1044

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
Cloudflare	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.

Operating System	Accuracy
FreeBSD 11.0-RELEASE	91%

Evidence

Software / Version	Category
WordPress	CMS, Blogs
Slider Revolution 6.6.19	Widgets, Photo galleries
MySQL	Databases
PHP	Programming languages
YouTube	Video players
GSAP	JavaScript frameworks
OceanWP 4.0.3	WordPress themes
Elementor 3.35.7	Page builders, WordPress plugins
Yoast SEO 27.1.1	SEO, WordPress plugins
Magnific Popup 4.0.3	JavaScript libraries
Lightbox	JavaScript libraries
imagesLoaded 5.0.0	JavaScript libraries
Elfsight	Widgets
Cloudflare Browser Insights	Analytics, RUM
Twitter Emoji (Twemoji)	Font scripts
Swiper	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
jQuery Migrate 3.4.1	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Google Tag Manager	Tag managers
Flickity	JavaScript libraries
Facebook Pixel 2.9.281	Analytics
core-js 3.46.0	JavaScript libraries
Google Font API	Font scripts
Google Analytics	Analytics
SiteGround	PaaS, Hosting
Cloudflare	CDN
RSS	Miscellaneous
Open Graph	Miscellaneous
HTTP/3	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.