Vulnerability Scan Result

Target:

http://enr.com/ (redirect)

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

Submitted: May 12, 2026 from HT

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Engineering News-Record \| ENR
Description:	ENR.com is the bible of the construction industry, providing news and features about projects, products and people in construction, architecture and engineering.

IP Information

ip_address	188.114.97.7
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	188.114.96.7
country	-
network_name	Cloudflare, Inc.
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	Cloudflare http proxy -
2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	https	Cloudflare http proxy -

Web Technologies

Software / Version	Category
Google Publisher Tag	Advertising
Google Font API	Font scripts
jQuery Migrate 1.4.1	JavaScript libraries
core-js 2.6.12	JavaScript libraries
HTTP/3	Miscellaneous
jQuery 3.2.1	JavaScript libraries
Modernizr 2.8.3	JavaScript libraries
MySQL	Databases
OneSignal	Marketing automation, A/B Testing
PHP	Programming languages
RequireJS 2.1.10	JavaScript frameworks
Ruby	Programming languages
Ruby on Rails	Web frameworks
Selectize	JavaScript libraries
Stimulus	JavaScript frameworks
DoubleClick Floodlight	Advertising
PWA	Miscellaneous
Webpack	Miscellaneous
Priority Hints	Performance
Enquire.js	JavaScript libraries
Headroom.js	Widgets, JavaScript libraries
WordPress	CMS, Blogs
Cloudflare	CDN
Google Tag Manager	Tag managers
OneTrust	Cookie compliance
HSTS	Security
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.enr.com/articles/62936-enrs-national-top-20-under-40-are-ready-to-meet-market-demands	role	Set-Cookie: .enr.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
OWASP Top 10 - 2021

Evidence

URL	Cookie Name	Evidence
https://www.enr.com/articles/62936-enrs-national-top-20-under-40-are-ready-to-meet-market-demands	cart.item_count, _utz_jpvc, user_ip_covered, last_viewed_path, role	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: cart.item_count=0 Set-Cookie: _utz_jpvc=BAhJIgYwBjoGRVQ%3D--0e501f009ae49b89a6dd427c0e3f4351763d026b Set-Cookie: user_ip_covered=false Set-Cookie: last_viewed_path=%2Farticles%2F62936-enrs-national-top-20-under-40-are-ready-to-meet-market-demands Set-Cookie: role=BAhJIgpndWVzdAY6BkVU--ebe11119fba476b33f2acd704b05aae1d1d99655

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.439	0.97566	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.02391	0.85149	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.02362	0.85058	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

Software / Version	Category
Google Publisher Tag	Advertising
Google Font API	Font scripts
jQuery Migrate 1.4.1	JavaScript libraries
core-js 2.6.12	JavaScript libraries
HTTP/3	Miscellaneous
jQuery 3.2.1	JavaScript libraries
Modernizr 2.8.3	JavaScript libraries
MySQL	Databases
OneSignal	Marketing automation, A/B Testing
PHP	Programming languages
RequireJS 2.1.10	JavaScript frameworks
Ruby	Programming languages
Ruby on Rails	Web frameworks
Selectize	JavaScript libraries
Stimulus	JavaScript frameworks
DoubleClick Floodlight	Advertising
PWA	Miscellaneous
Webpack	Miscellaneous
Priority Hints	Performance
Enquire.js	JavaScript libraries
Headroom.js	Widgets, JavaScript libraries
WordPress	CMS, Blogs
Cloudflare	CDN
Google Tag Manager	Tag managers
OneTrust	Cookie compliance
HSTS	Security
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

URL	Evidence
https://www.enr.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. 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'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'.

https://www.enr.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. 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'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it 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-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://www.enr.com/authors/192-alisa-zevin	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 Cookies: _enr_session=BAh7CUkiD3Nlc3Npb25faWQGOgZFVEkiJWZlYmQwMDY4NDVhZDM0NjQ5OTYyZGVhNDI3YjNlZDYwBjsAVEkiCGtleQY7AEZJIikwZDgzZGMyNy0xZmFlLTRhOGEtYWJlM...	Suspicious message under construction found in: `er construction site in Hutto, Texas. data center under construction beside electrical transmission infrastructure." t`

Vulnerability description

We noticed that the target application's debug messages reveal unnecessary information about the system's internal state. For example, debug data in design can be exposed through internal memory array dumps or boot logs through interfaces like UART via TAP commands, scan chain, etc. Thus, the more information contained in a debug message, the easier it is to debug.

Risk description

The risk of revealing debug information is that it could help an attacker either decipher a vulnerability, and/or gain a better understanding of the system. Thus, this extra information could lower the “security by obscurity” factor. While “security by obscurity” alone is insufficient, it can help as a part of “Defense-in-depth”.

Recommendation

Ensure that a debug message does not reveal any unnecessary information during the debug process for the intended response.

Classification

CWE	CWE-1295
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://www.enr.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
https://www.enr.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.enr.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	Operating system paths found in the HTTP response: `/media/podcasts/1090-enr-groundbreakers-podcast/play/155-sto-building-group-ceo-reveals-innovation-behind-three-new-business-lines-it-s-all-about-the-additional-services-we-can-offer` `/media/podcasts` `/media/podcasts/1090-enr-groundbreakers-podcast/play/156-stv-ceo-announces-plan-to-launch-new-power-business` `/media/podcasts/781`

Vulnerability description

We found operating system paths returned in a HTTP response.

Risk description

The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.

Recommendation

Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.

Classification

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

Evidence

URL	Method	Parameters	Evidence
https://www.enr.com/articles/62986-ireland-splits-18b-metrolink-procurement-into-separate-civil-rail-systems-packages	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 Cookies: _enr_session=BAh7CUkiD3Nlc3Npb25faWQGOgZFVEkiJWZlYmQwMDY4NDVhZDM0NjQ5OTYyZGVhNDI3YjNlZDYwBjsAVEkiCGtleQY7AEZJIikwZDgzZGMyNy0xZmFlLTRhOGEtYWJlM...	Email Address: gottliebb@enr.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.enr.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

Software / Version	Category
WordPress	CMS, Blogs
Ruby	Programming languages
MySQL	Databases
PHP	Programming languages
Ruby on Rails	Web frameworks
Stimulus	JavaScript frameworks
OneTrust	Cookie compliance
OneSignal	Marketing automation, A/B Testing
Modernizr	JavaScript libraries
jQuery	JavaScript libraries
Headroom.js	Widgets, JavaScript libraries
Google Tag Manager	Tag managers
Google Publisher Tag	Advertising
Enquire.js	JavaScript libraries
DoubleClick Floodlight	Advertising
HSTS	Security
Cloudflare	CDN
HTTP/3	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.

Evidence

Software / Version	Category
Cloudflare	CDN

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.enr.com	A	IPv4 address	188.114.97.7
www.enr.com	A	IPv4 address	188.114.96.7
www.enr.com	AAAA	IPv6 address	2a06:98c1:3120::7
www.enr.com	AAAA	IPv6 address	2a06:98c1:3121::7

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
Cloudflare	CDN

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
Cloudflare	CDN

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.