Vulnerability Scan Result

Target:

http://randstad.com/ (redirect)

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

Submitted: Apr 19, 2026 from KM

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	The global leader in the HR services industry \| Randstad
Description:	Randstad is the global leader in the HR services industry. By combining our passion for people with the power of today’s intelligent machines, we support people and organizations in realizing their true potential. Learn more about our company.

IP Information

ip_address	52.85.47.32
country	US
network_name	Amazon.com, Inc.
asn	AS16509

ip_address	52.85.47.46
country	US
network_name	Amazon.com, Inc.
asn	AS16509

ip_address	52.85.47.79
country	US
network_name	Amazon.com, Inc.
asn	AS16509

ip_address	52.85.47.85
country	US
network_name	Amazon.com, Inc.
asn	AS16509

Open Ports

80/tcp	http	Amazon CloudFront httpd -
443/tcp	https	- -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Amazon S3	CDN
Babel	Miscellaneous
Microsoft Clarity	Analytics
core-js 2.6.12	JavaScript libraries
Google Analytics	Analytics
jQuery 3.7.1	JavaScript libraries
LottieFiles 5.3.1	Miscellaneous
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
React 18.2.0	JavaScript frameworks
DoubleClick Floodlight	Advertising
Unpkg	CDN
WordPress	CMS, Blogs
Drupal	CMS
reCAPTCHA	Security
Google Tag Manager	Tag managers
OneTrust	Cookie compliance
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.randstad.com/	ip_address, cms_user_id	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: ip_address=172.236.195.218 Set-Cookie: cms_user_id=WxhF1x20s2hhUjsu

Vulnerability description

We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation

Ensure that the HttpOnly flag is set for all cookies.

Classification

CWE	CWE-1004
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Amazon S3	CDN
Babel	Miscellaneous
Microsoft Clarity	Analytics
core-js 2.6.12	JavaScript libraries
Google Analytics	Analytics
jQuery 3.7.1	JavaScript libraries
LottieFiles 5.3.1	Miscellaneous
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
React 18.2.0	JavaScript frameworks
DoubleClick Floodlight	Advertising
Unpkg	CDN
WordPress	CMS, Blogs
Drupal	CMS
reCAPTCHA	Security
Google Tag Manager	Tag managers
OneTrust	Cookie compliance
HSTS	Security

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
https://www.randstad.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 Evidence

URL	Evidence
https://www.randstad.com/	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. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. 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'.`

https://www.randstad.com/

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. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. 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'.

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

URL	Evidence
https://www.randstad.com/sites/default/	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
Missing: https://www.randstad.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

Evidence

URL	Method	Parameters	Evidence
https://www.randstad.com/terms-and-conditions/	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 Cookies: cms_user_id=mKemtgL80MSrOyE9 cms_user_id_httponly=mKemtgL80MSrOyE9 ip_address=172.236.195.218 userSessionID=QzuYUSIlzyaS5uma	Email Address: privacyofficer@randstad.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

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.randstad.com	A	IPv4 address	52.85.47.32
www.randstad.com	A	IPv4 address	52.85.47.46
www.randstad.com	A	IPv4 address	52.85.47.79
www.randstad.com	A	IPv4 address	52.85.47.85

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
Crestron XPanel control system	87%

Evidence

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Amazon Web Services	PaaS
Unpkg	CDN
OneTrust	Cookie compliance
Google Tag Manager	Tag managers
Google Analytics	Analytics
DoubleClick Floodlight	Advertising
reCAPTCHA	Security
HSTS	Security
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon S3	CDN
Amazon CloudFront	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.