Vulnerability Scan Result

Target:

https://www.bloombergmedia.com/contact/?utm_medium=email&utm_source=newsletter&utm_campaign=weekend

Scanned target: https://www.bloombergmedia.com/contact/?utm_medium=email&utm_source=newsletter&utm_campaign=weekend

Submitted: Aug 17, 2025 from LA

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Contact \| Bloomberg Media
Description:	Intelligence for the new era of business. @BBGMedia

IP Information

ip_address	151.101.1.73
country	US
network_name	Fastly Inc
asn	AS54113

ip_address	151.101.65.73
country	US
network_name	Fastly Inc
asn	AS54113

ip_address	151.101.129.73
country	US
network_name	Fastly Inc
asn	AS54113

ip_address	151.101.193.73
country	US
network_name	Fastly Inc
asn	AS54113

Open Ports

80/tcp	http	Varnish -
443/tcp	https	- -

Web Technologies

No technologies could be detected.

Web Application Vulnerabilities

Evidence

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

https://www.bloombergmedia.com/contact/

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

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
OWASP Top 10 - 2021

Evidence

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

Evidence

URL	Method	Parameters	Evidence
https://www.bloombergmedia.com/contact/	GET	Query: utm_campaign=weekend utm_medium=email utm_source=newsletter 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: dbradford11@bloomberg.net adsalesleads@bloomberg.net apacmedia@bloomberg.net dpedraza13@bloomberg.net virtualevent@bloomberg.net ssoares5@bloomberg.net

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

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Varnish	Caching
Nginx	Web servers, Reverse proxies
wpBakery	Page builders, WordPress plugins
Yoast SEO 19.11	SEO, WordPress plugins
Twitter	Widgets
jQuery Migrate 3.4.1	JavaScript libraries
jQuery	JavaScript libraries
ipify	Geolocation
Google Tag Manager	Tag managers
Google Analytics	Analytics
HSTS	Security
DigiCert	SSL/TLS certificate authorities

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.

Operating System	Accuracy
Crestron XPanel control system	90%

Evidence

Domain Queried	DNS Record Type	Description	Value
www.bloombergmedia.com	A	IPv4 address	151.101.1.73
www.bloombergmedia.com	A	IPv4 address	151.101.65.73
www.bloombergmedia.com	A	IPv4 address	151.101.129.73
www.bloombergmedia.com	A	IPv4 address	151.101.193.73
www.bloombergmedia.com	CNAME	Canonical name	www.bloombergmedia.com.shared.bloomberga.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.