Vulnerability Scan Result

Target:

https://tracking.babypark.nl/vestigingen.html?utm_source=email&utm_medium=campaign&utm_campaign=WK16_2025_Vrolijk_Pasen&eyk_source=email&eyk_campaign=WK16_2025_Vrolijk_Pasen&eyk_id=WK16_2025_Vrolijk_Pasen&cdmtw=QAAIAAIYCICCoCQaFGlGqwC9MXCCxiwAlWrUqA (redirect)

Scanned target: https://www.babypark.nl/vestigingen.html?utm_source=email&utm_medium=campaign&utm_campaign=WK16_2025_Vrolijk_Pasen&eyk_source=email&eyk_campaign=WK16_2025_Vrolijk_Pasen&eyk_id=WK16_2025_Vrolijk_Pasen

Submitted: April 18, 2025 from MC

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

https://tracking.babypark.nl/vestigingen.html?utm_source=email&utm_medium=campaign&utm_campaign=WK16_2025_Vrolijk_Pasen&eyk_source=email&eyk_campaign=WK16_2025_Vrolijk_Pasen&eyk_id=WK16_2025_Vrolijk_Pasen&cdmtw=QAAIAAIYCICCoCQaFGlGqwC9MXCCxiwAlWrUqA

Title:	Onze Babypark vestigingen \| Babypark
Description:	Babypark megastores vind je verspreid door heel Nederland. Ook vind je een megastore in Duitsland. Zo heb je altijd een winkel in de buurt voor jou babyuitzet!

IP Information

IP address	185.131.27.1
Country	NL
AS number	AS60781
Net name	Leaseweb Netherlands B.V

Open Ports

25/tcp	smtp	Postfix smtpd -
80/tcp	http	Apache -
443/tcp	https	Apache -
587/tcp	smtp	Postfix smtpd -
993/tcp	imaps	- -
995/tcp	pop3s	- -

Web Technologies

Software / Version	Category
Microsoft Advertising	Advertising
Animate.css	UI frameworks
Matter.js	JavaScript libraries
Magnific Popup	JavaScript libraries
ElasticSuite	Search engines
Facebook Pixel 2.9.198	Analytics
Adobe Fonts	Font scripts
Bootstrap	UI frameworks
jQuery Migrate	JavaScript libraries
core-js 3.32.2	JavaScript libraries
Google Analytics	Analytics
jQuery	JavaScript libraries
jQuery UI 1.10.4	JavaScript libraries
Lightbox	JavaScript libraries
Magento CE 2.4.2 - 2.4.2-p2	Ecommerce
Moment.js	JavaScript libraries
MySQL	Databases
New Relic	RUM
Nginx	Web servers, Reverse proxies
OWL Carousel	JavaScript libraries
PHP	Programming languages
RequireJS	JavaScript frameworks
Typekit	Font scripts
Underscore.js	JavaScript libraries
AWIN	Affiliate programs
Cookie Control	Cookie compliance
Cookiebot	Cookie compliance
Elasticsearch	Search engines
Google Tag Manager	Tag managers
Klevu 1	Search engines
HSTS	Security
Smartlook	Analytics
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

CVSS	CVE	Summary	Affected software
10	CVE-2022-24086	Adobe Commerce versions 2.4.3-p1 (and earlier) and 2.3.7-p2 (and earlier) are affected by an improper input validation vulnerability during the checkout process. Exploitation of this issue does not require user interaction and could result in arbitrary code execution.	magento 2.4.2
9.8	CVE-2022-34256	Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improper Authorization vulnerability that could result in Privilege escalation. An attacker could leverage this vulnerability to access other user's data. Exploitation of this issue does not require user interaction.	magento 2.4.2
8.8	CVE-2022-34254	Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could be abused by an attacker to inject malicious scripts into the vulnerable endpoint. A low privileged attacker could leverage this vulnerability to read local files and to perform Stored XSS. Exploitation of this issue does not require user interaction.	magento 2.4.2
8.8	CVE-2022-34255	Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improper Access Control vulnerability that could result in Privilege escalation. An attacker with a low privilege account could leverage this vulnerability to perform an account takeover for a victim. Exploitation of this issue does not require user interaction.	magento 2.4.2
8.8	CVE-2022-42344	Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Incorrect Authorization vulnerability. An authenticated attacker can exploit this vulnerability to achieve information exposure and privilege escalation.	magento 2.4.2
6.1	CVE-2022-31160	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`.	jquery_ui 1.10.4
4.3	CVE-2016-7103	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.	jquery_ui 1.10.4
4.3	CVE-2021-41182	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.	jquery_ui 1.10.4
4.3	CVE-2021-41183	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.	jquery_ui 1.10.4
4.3	CVE-2021-41184	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.	jquery_ui 1.10.4

Vulnerability description

We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.

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.

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-1026
OWASP Top 10 - 2017	A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2021	A6 - Vulnerable and Outdated Components

Evidence

URL	Cookie Name	Evidence
https://www.babypark.nl/vestigingen.html	SERVERIDM1	Set-Cookie: SERVERIDM1=green

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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Cookie Name	Evidence
https://www.babypark.nl/vestigingen.html	_sbp, SERVERIDM1	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: _sbp=8bb9e0f503f46159d76701a147161db23150069afbf59f0c0c565de79f057d1d Set-Cookie: SERVERIDM1=green

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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Cookie Name	Evidence
https://www.babypark.nl/vestigingen.html	_sbp	Set-Cookie: .babypark.nl

Vulnerability description

We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.

Risk description

The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.

Recommendation

The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`

Classification

CWE	CWE-614
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://www.babypark.nl/vestigingen.html	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-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://www.babypark.nl/vestigingen.html	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
Microsoft Advertising	Advertising
Animate.css	UI frameworks
Matter.js	JavaScript libraries
Magnific Popup	JavaScript libraries
ElasticSuite	Search engines
Facebook Pixel 2.9.198	Analytics
Adobe Fonts	Font scripts
Bootstrap	UI frameworks
jQuery Migrate	JavaScript libraries
core-js 3.32.2	JavaScript libraries
Google Analytics	Analytics
jQuery	JavaScript libraries
jQuery UI 1.10.4	JavaScript libraries
Lightbox	JavaScript libraries
Magento CE 2.4.2 - 2.4.2-p2	Ecommerce
Moment.js	JavaScript libraries
MySQL	Databases
New Relic	RUM
Nginx	Web servers, Reverse proxies
OWL Carousel	JavaScript libraries
PHP	Programming languages
RequireJS	JavaScript frameworks
Typekit	Font scripts
Underscore.js	JavaScript libraries
AWIN	Affiliate programs
Cookie Control	Cookie compliance
Cookiebot	Cookie compliance
Elasticsearch	Search engines
Google Tag Manager	Tag managers
Klevu 1	Search engines
HSTS	Security
Smartlook	Analytics
Cart Functionality	Ecommerce

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

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL
https://www.babypark.nl/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).

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

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

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
tracking.babypark.nl	A	IPv4 address	185.131.27.1
tracking.babypark.nl	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
tracking.babypark.nl	CNAME	Canonical name	tracking.copernica.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.

Operating System
Linux 5.0 - 5.4

Evidence

Software / Version	Category
Apache HTTP Server	Web servers
Google Font API	Font scripts

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
Apache HTTP Server	Web servers
Google Font API	Font scripts

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.