Vulnerability Scan Result

Target:

http://placed.com/ (redirect)

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

Submitted: Jun 18, 2026 from KW

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Placed
Description:	No description found

IP Information

ip_address	54.146.1.94
country	US
network_name	Amazon.com, Inc.
asn	AS14618

ip_address	98.84.225.125
country	US
network_name	Amazon.com, Inc.
asn	AS14618

ip_address	44.219.132.29
country	US
network_name	Amazon.com, Inc.
asn	AS14618

ip_address	44.207.14.106
country	US
network_name	Amazon.com, Inc.
asn	AS14618

ip_address	3.233.30.189
country	US
network_name	Amazon.com, Inc.
asn	AS14618

ip_address	52.20.136.115
country	US
network_name	Amazon.com, Inc.
asn	AS14618

Open Ports

80/tcp	http	awselb/2.0 -
443/tcp	https	awselb/2.0 -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Babel	Miscellaneous
core-js 2.6.12	JavaScript libraries
Google Analytics GA4	Analytics
MySQL	Databases
PHP	Programming languages
React	JavaScript frameworks
Ruby	Programming languages
Ruby on Rails	Web frameworks
DoubleClick Floodlight	Advertising
WordPress	CMS, Blogs
Google Tag Manager	Tag managers
Lodash 4.17.21	JavaScript libraries
HSTS	Security
Varnish	Caching

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2026-4800	8.1	0.01735	0.74822	Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for the variable option in _.template but did not apply the same validation to options.imports key names. Both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in. If Object.prototype has been polluted by any other vector, the polluted keys are copied into the imports object and passed to Function(). Patches: Users should upgrade to version 4.18.0. Workarounds: Do not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names.
CVE-2025-13465	6.9	0.01535	0.7169	Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. This issue is patched on 4.17.23
CVE-2026-2950	6.5	0.00317	0.23446	Impact: Lodash versions 4.17.23 and earlier are vulnerable to prototype pollution in the _.unset and _.omit functions. The fix for (CVE-2025-13465: https://github.com/lodash/lodash/security/advisories/GHSA-xxjr-mmjv-4gpg) only guards against string key members, so an attacker can bypass the check by passing array-wrapped path segments. This allows deletion of properties from built-in prototypes such as Object.prototype, Number.prototype, and String.prototype. The issue permits deletion of prototype properties but does not allow overwriting their original behavior. Patches: This issue is patched in 4.18.0. Workarounds: None. Upgrade to the patched version.

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	Cookie Name	Evidence
https://www.placed.com/	_rails-website_session	Set-Cookie: _rails-website_session=V0t4TVpPcytlN09hbGQ2cFQ1OE1nKzE1U3JwMnRnMlprdjZrY1FIUHRqc0N1b0NRNjVXM0xGakM0b0Mrc3d0VlBNNUtwT1lKdDViMW9WSXdGaHdMZFhNZldlaFNUYmhDTVpTbk80QytuRTZueW9JSG5BbExkUVVnZGFneEd4N2R4cGcrQlVKU25EY29zR2ZFSG9VdTlZb3g0S0JnNlRIaU5TV3lkcjZWSXdXbGlqc1kvQWlHa0JadGZ2cFFQN2lvLS15V3JHaDNpMXZkVWpzcnZZWnJNMW9nPT0%3D--c5ba281b18be883b3370453d4fb16667e4674913

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

Software / Version	Category
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Babel	Miscellaneous
core-js 2.6.12	JavaScript libraries
Google Analytics GA4	Analytics
MySQL	Databases
PHP	Programming languages
React	JavaScript frameworks
Ruby	Programming languages
Ruby on Rails	Web frameworks
DoubleClick Floodlight	Advertising
WordPress	CMS, Blogs
Google Tag Manager	Tag managers
Lodash 4.17.21	JavaScript libraries
HSTS	Security
Varnish	Caching

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.placed.com/	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.placed.com/	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
Missing: https://developer.foursquare.com/.well-known/security

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

Infrastructure Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	CISA KEV	Summary
CVE-2026-4800	8.1	0.01735	0.74822	No	Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for the variable option in _.template but did not apply the same validation to options.imports key names. Both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in. If Object.prototype has been polluted by any other vector, the polluted keys are copied into the imports object and passed to Function(). Patches: Users should upgrade to version 4.18.0. Workarounds: Do not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names.
CVE-2025-13465	6.9	0.01535	0.7169	No	Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. This issue is patched on 4.17.23
CVE-2026-2950	6.5	0.00317	0.23446	No	Impact: Lodash versions 4.17.23 and earlier are vulnerable to prototype pollution in the _.unset and _.omit functions. The fix for (CVE-2025-13465: https://github.com/lodash/lodash/security/advisories/GHSA-xxjr-mmjv-4gpg) only guards against string key members, so an attacker can bypass the check by passing array-wrapped path segments. This allows deletion of properties from built-in prototypes such as Object.prototype, Number.prototype, and String.prototype. The issue permits deletion of prototype properties but does not allow overwriting their original behavior. Patches: This issue is patched in 4.18.0. Workarounds: None. Upgrade to the patched version.

Vulnerability description

Vulnerabilities found for Lodash 4.17.21

Risk description

These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; 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

We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.

Evidence

Software / Version	Category
WordPress	CMS, Blogs
Ruby	Programming languages
MySQL	Databases
PHP	Programming languages
Ruby on Rails	Web frameworks
Varnish	Caching
Amazon Web Services	PaaS
React	JavaScript frameworks
Lodash 4.17.21	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
core-js 2.6.12	JavaScript libraries
DoubleClick Floodlight	Advertising
AWS Certificate Manager	SSL/TLS certificate authorities
Babel	Miscellaneous
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.

Evidence

Domain Queried	DNS Record Type	Description	Value
www.placed.com	A	IPv4 address	44.207.14.106
www.placed.com	A	IPv4 address	3.233.30.189
www.placed.com	A	IPv4 address	52.20.136.115
www.placed.com	A	IPv4 address	54.146.1.94
www.placed.com	A	IPv4 address	98.84.225.125
www.placed.com	A	IPv4 address	44.219.132.29
www.placed.com	TXT	Text record	"heritage=external-dns,external-dns/owner=my-hostedzone-identifier,external-dns/resource=ingress/mint-production/mint-production"
www.placed.com	CNAME	Canonical name	placed.ea-use1-eaeksprod.k8s.4sqi.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.