Vulnerability Scan Result

Target:

https://hello.pros.com/api/mailings/click/PMRGSZBCHIZTGOJVGAZCYITVOJWCEORCNB2HI4B2F4XXO53XFZYHE33TFZRW63JPEIWCE33SM4RDUITGGIZWCZRQMY3S2NJRMVSS2NDEMNRS2OJUMY2S2NRWMQYTMNLFHAYGKOBQEIWCE5TFOJZWS33OEI5CENBCFQRHG2LHEI5CESDMIJTHARTCMRXEI5LGN5LUWM2KGJ5EIQ3SNVJESXZQK5XU2SCMI43VU2DHIQYW6YLJNM6SE7I= (redirect)

Scanned target: https://pros.com/

Submitted: April 18, 2025 from BE

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

https://hello.pros.com/api/mailings/click/PMRGSZBCHIZTGOJVGAZCYITVOJWCEORCNB2HI4B2F4XXO53XFZYHE33TFZRW63JPEIWCE33SM4RDUITGGIZWCZRQMY3S2NJRMVSS2NDEMNRS2OJUMY2S2NRWMQYTMNLFHAYGKOBQEIWCE5TFOJZWS33OEI5CENBCFQRHG2LHEI5CESDMIJTHARTCMRXEI5LGN5LUWM2KGJ5EIQ3SNVJESXZQK5XU2SCMI43VU2DHIQYW6YLJNM6SE7I=

Title:	PROS Real-time Enterprise AI
Description:	The PROS SaaS platform powers profitable growth for the world’s leading companies with the planet’s most advanced neural network AI technology.

IP Information

IP address	44.217.81.166
Country	US
AS number	AS14618
Net name	Amazon Inc

IP address	54.234.216.115
Country	US
AS number	AS14618
Net name	Amazon Inc

IP address	44.208.39.128
Country	US
AS number	AS14618
Net name	Amazon Inc

Open Ports

80/tcp	http	nginx -
443/tcp	https	nginx -

Web Technologies

Software / Version	Category
Reddit Ads	Advertising
Amazon Web Services	PaaS
Linkedin Insight Tag	Analytics
Elementor 3.28.1	Page builders, WordPress plugins
FancyBox	JavaScript libraries
Google Analytics GA4	Analytics
jQuery 3.7.1	JavaScript libraries
MySQL	Databases
Pagely	PaaS, Hosting
PHP	Programming languages
PyScript	Miscellaneous
Python	Programming languages
Swiper	JavaScript libraries
Basic	Security
Wistia	Video players
WordPress	CMS, Blogs
Demandbase	Analytics, Personalisation
reCAPTCHA	Security
Google Tag Manager	Tag managers
Marketo 164	Marketing automation
MyFonts	Font scripts
OneTrust	Cookie compliance
HSTS	Security
Yoast SEO 24.7	SEO, WordPress plugins

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://pros.com/	_sbp	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: _sbp=6382cd80f2e6333dd8a738c5e9561bd1

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://pros.com/	_sbp	Set-Cookie: .pros.com

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

URL	Evidence
https://pros.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: https: URI in default-src allows the execution of unsafe scripts. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. 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'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). object-src: We recommend restricting object-src to 'none'.

https://pros.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: https: URI in default-src allows the execution of unsafe scripts. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. 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'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). object-src: We recommend restricting object-src to 'none'.

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

Evidence

Software / Version	Category
Reddit Ads	Advertising
Amazon Web Services	PaaS
Linkedin Insight Tag	Analytics
Elementor 3.28.1	Page builders, WordPress plugins
FancyBox	JavaScript libraries
Google Analytics GA4	Analytics
jQuery 3.7.1	JavaScript libraries
MySQL	Databases
Pagely	PaaS, Hosting
PHP	Programming languages
PyScript	Miscellaneous
Python	Programming languages
Swiper	JavaScript libraries
Basic	Security
Wistia	Video players
WordPress	CMS, Blogs
Demandbase	Analytics, Personalisation
reCAPTCHA	Security
Google Tag Manager	Tag managers
Marketo 164	Marketing automation
MyFonts	Font scripts
OneTrust	Cookie compliance
HSTS	Security
Yoast SEO 24.7	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

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

Evidence

URL
https://pros.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).

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
hello.pros.com	A	IPv4 address	54.234.216.115
hello.pros.com	A	IPv4 address	44.208.39.128
hello.pros.com	A	IPv4 address	44.217.81.166
hello.pros.com	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
hello.pros.com	CNAME	Canonical name	f23af0f7-51ee-4dcc-94f5-66d165e80e80.outrch.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
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.