Vulnerability Scan Result

Target:

https://www.cityoftaylor.com/ (redirect)

Scanned target: https://www.cityoftaylor.com/1414/Portal

Submitted: May 15, 2026 from GA

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Portal \| Taylor, MI
Description:

IP Information

ip_address	208.90.188.225
country	US
network_name	IP Pathways, LLC
asn	AS36489

Open Ports

80/tcp	http	Microsoft HTTPAPI httpd 2
443/tcp	https	- -

Web Technologies

Software / Version	Category
Alpine.js 3.14.1	JavaScript frameworks
Amazon Web Services	PaaS
Azure	PaaS
Azure Monitor	Analytics, Performance
Font Awesome	Font scripts
Google Font API	Font scripts
Froala Editor 2+	Rich text editors
Bootstrap	UI frameworks
jQuery Migrate 3.5.2	JavaScript libraries
core-js 3.49.0	JavaScript libraries
Google Analytics GA4	Analytics
Htmx	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.14.1	JavaScript libraries
Modernizr 2.5.3	JavaScript libraries
Moment.js 2.30.1	JavaScript libraries
MySQL	Databases
PHP	Programming languages
DoubleClick Floodlight	Advertising
UserWay	Accessibility
WordPress	CMS, Blogs
AudioEye	Accessibility
CivicPlus	CMS
Google Tag Manager	Tag managers

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.cityoftaylor.com/1414/Portal	CP_IsMobile	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: CP_IsMobile=false

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

URL	Cookie Name	Evidence
https://www.cityoftaylor.com/1414/Portal	CP_IsMobile, ASP.NET_SessionId	Set-Cookie: CP_IsMobile=false Set-Cookie: ASP.NET_SessionId=xljl1t2242ngesu3cqy2thub

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
Alpine.js 3.14.1	JavaScript frameworks
Amazon Web Services	PaaS
Azure	PaaS
Azure Monitor	Analytics, Performance
Font Awesome	Font scripts
Google Font API	Font scripts
Froala Editor 2+	Rich text editors
Bootstrap	UI frameworks
jQuery Migrate 3.5.2	JavaScript libraries
core-js 3.49.0	JavaScript libraries
Google Analytics GA4	Analytics
Htmx	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.14.1	JavaScript libraries
Modernizr 2.5.3	JavaScript libraries
Moment.js 2.30.1	JavaScript libraries
MySQL	Databases
PHP	Programming languages
DoubleClick Floodlight	Advertising
UserWay	Accessibility
WordPress	CMS, Blogs
AudioEye	Accessibility
CivicPlus	CMS
Google Tag Manager	Tag managers

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.cityoftaylor.com/1414/Portal	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.cityoftaylor.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
https://www.cityoftaylor.com/1414/Portal	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 Evidence

URL	Evidence
https://www.cityoftaylor.com/1414/Portal	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: default-src should not allow '' as source. This may enable execution of malicious JavaScript. 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(). script-src: script-src should not allow '' as source. This may enable execution of malicious JavaScript. object-src: We recommend restricting object-src to 'none'. 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'.

https://www.cityoftaylor.com/1414/Portal

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. 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(). script-src: script-src should not allow '*' as source. This may enable execution of malicious JavaScript. object-src: We recommend restricting object-src to 'none'. 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'.

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

Domain Queried	DNS Record Type	Description	Value
www.cityoftaylor.com	A	IPv4 address	208.90.188.225
www.cityoftaylor.com	NS	Name server	pdns13.domaincontrol.com
www.cityoftaylor.com	NS	Name server	pdns14.domaincontrol.com
www.cityoftaylor.com	SOA	Start of Authority	pdns13.domaincontrol.com. dns.jomax.net. 2025082500 28800 7200 604800 600
www.cityoftaylor.com	TXT	Text record	"cj5i40pbk1boafsn68mn7prhi3"
www.cityoftaylor.com	TXT	Text record	"1n66b5kt3knqa04pq6qaclacb3"
www.cityoftaylor.com	CNAME	Canonical name	cityoftaylor.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
WordPress	CMS, Blogs
CivicPlus	CMS
MySQL	Databases
PHP	Programming languages
Bootstrap	UI frameworks
Azure	PaaS
Alpine.js	JavaScript frameworks
Amazon Web Services	PaaS
UserWay	Accessibility
Moment.js	JavaScript libraries
jQuery UI 1.14.1	JavaScript libraries
jQuery Migrate 3.5.2	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Azure Monitor	Analytics, Performance
AudioEye	Accessibility
DoubleClick Floodlight	Advertising

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
WordPress	CMS, Blogs
CivicPlus	CMS
MySQL	Databases
PHP	Programming languages
Bootstrap	UI frameworks
Azure	PaaS
Alpine.js	JavaScript frameworks
Amazon Web Services	PaaS
UserWay	Accessibility
Moment.js	JavaScript libraries
jQuery UI 1.14.1	JavaScript libraries
jQuery Migrate 3.5.2	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Azure Monitor	Analytics, Performance
AudioEye	Accessibility
DoubleClick Floodlight	Advertising

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.