Vulnerability Scan Result

Target:

https://centerpointpost.com/ (redirect)

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

Submitted: Jun 14, 2026 from RW

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Center Point Post
Description:	Cinema/Television Post Production Support Company and Live Events Services

IP Information

ip_address	198.185.159.144
country	US
network_name	Squarespace, Inc.
asn	AS53831

ip_address	198.49.23.145
country	US
network_name	Squarespace, Inc.
asn	AS53831

ip_address	198.185.159.145
country	US
network_name	Squarespace, Inc.
asn	AS53831

ip_address	198.49.23.144
country	US
network_name	Squarespace, Inc.
asn	AS53831

Open Ports

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

Web Technologies

Software / Version	Category
cdnjs	CDN
YUI 3.17.2	JavaScript libraries
Adobe Fonts 1.21.0	Font scripts
Google Font API	Font scripts
parallax.js	JavaScript libraries
core-js 3.26.0	JavaScript libraries
jQuery 3.2.1	JavaScript libraries
lit-element 3.1.2	JavaScript libraries
LottieFiles	Miscellaneous
Modernizr 2.8.3	JavaScript libraries
Open Graph	Miscellaneous
Sentry	Issue trackers
Statsig 3.33.2	Analytics, Feature management
Stimulus	JavaScript frameworks
Typekit 1.21.0	Font scripts
Unpkg	CDN
Priority Hints	Performance
Cloudflare	CDN
reCAPTCHA	Security
jsDelivr	CDN
HSTS	Security
Squarespace 7.1	CMS
Squarespace Commerce 7.1	Ecommerce
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.centerpointpost.com/	crumb	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: crumb=BWmrq0gOBudINzFkMTM3Y2NhYmQ2ZmI0OGU4MWNiOGQ5YWY0YWIy

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

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2020-11023	6.9	0.8383	0.99653	In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11022	6.9	0.99019	0.99925	In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2019-11358	6.1	0.87218	0.99726	jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.

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.centerpointpost.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
https://www.centerpointpost.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	Method	Parameters	Evidence
https://www.centerpointpost.com/	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	`1 : <link rel="image_src" href="http://static1.squarespace.com/static/645c16c1ccbd953ee66edbec/t/645c16caccbd953ee66edd21/1768358773808/SOCIAL+SHARING+FINAL+copy.jpg?format=1500w">`

Vulnerability description

We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.

Risk description

The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.

Recommendation

Ensure that all external resources the page references are loaded using HTTPS.

Classification

CWE	CWE-319
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
cdnjs	CDN
YUI 3.17.2	JavaScript libraries
Adobe Fonts 1.21.0	Font scripts
Google Font API	Font scripts
parallax.js	JavaScript libraries
core-js 3.26.0	JavaScript libraries
jQuery 3.2.1	JavaScript libraries
lit-element 3.1.2	JavaScript libraries
LottieFiles	Miscellaneous
Modernizr 2.8.3	JavaScript libraries
Open Graph	Miscellaneous
Sentry	Issue trackers
Statsig 3.33.2	Analytics, Feature management
Stimulus	JavaScript frameworks
Typekit 1.21.0	Font scripts
Unpkg	CDN
Priority Hints	Performance
Cloudflare	CDN
reCAPTCHA	Security
jsDelivr	CDN
HSTS	Security
Squarespace 7.1	CMS
Squarespace Commerce 7.1	Ecommerce
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

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

Evidence

URL	Evidence
https://www.centerpointpost.com/	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	Method	Parameters	Evidence
https://www.centerpointpost.com/	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	Email Address: user@domain.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

Evidence

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

Infrastructure Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	CISA KEV	Summary
CVE-2020-11023	6.9	0.8383	0.99653	Yes	In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11022	6.9	0.99019	0.99925	No	In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2019-11358	6.1	0.87218	0.99726	No	jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.

Vulnerability description

Vulnerabilities found for jQuery 3.2.1

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.

Operating System	Accuracy
FreeBSD 11.0-RELEASE	93%

Evidence

Domain Queried	DNS Record Type	Description	Value
www.centerpointpost.com	A	IPv4 address	198.185.159.144
www.centerpointpost.com	A	IPv4 address	198.49.23.145
www.centerpointpost.com	A	IPv4 address	198.185.159.145
www.centerpointpost.com	A	IPv4 address	198.49.23.144
www.centerpointpost.com	CNAME	Canonical name	ext-sq.squarespace.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
Cart Functionality	Ecommerce
Squarespace Commerce 7.1	Ecommerce
Squarespace 7.1	CMS
Sentry	Issue trackers
Stimulus	JavaScript frameworks
Cloudflare	CDN
Unpkg	CDN
parallax.js	JavaScript libraries
cdnjs	CDN
YUI 3.17.2	JavaScript libraries
Typekit 1.21.0	Font scripts
Statsig 3.33.2	Analytics, Feature management
Modernizr 2.8.3	JavaScript libraries
lit-html 2.1.2	JavaScript libraries
lit-element 3.1.2	JavaScript libraries
jQuery 3.2.1	JavaScript libraries
core-js 3.26.0	JavaScript libraries
Priority Hints	Performance
jsDelivr	CDN
Google Font API	Font scripts
Adobe Fonts 1.21.0	Font scripts
reCAPTCHA	Security
HSTS	Security
LottieFiles	Miscellaneous
Open Graph	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.