Vulnerability Scan Result

Target:

https://twopinesmissoula.org/ (redirect)

Scanned target: https://www.twopinesmissoula.org/

Submitted: May 03, 2026 from PA

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	Compassionate Support for the Wounded Soul \| Two Pines Missoula
Description:	Find compassionate, faith-rooted support for the wounded soul at Two Pines Missoula—offering spiritual care, healing rituals, and trauma-informed guidance.

IP Information

ip_address	143.244.56.50
country	FR
network_name	DataCamp Limited
asn	AS60068

Open Ports

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

Web Technologies

Software / Version	Category
All in One SEO 4.9.6.2	SEO, WordPress plugins
Animate.css	UI frameworks
Amazon Web Services	PaaS
Amazon S3	CDN
Bunny	CDN
Calendly	Appointment scheduling
Clipboard.js	JavaScript libraries
Elementor 4.0.4	Page builders, WordPress plugins
Font Awesome	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
Mailcheck 1.1.2	JavaScript libraries
punycode 1.0.0	JavaScript libraries
PubSubJS 3.4.0	JavaScript libraries
core-js 3.46.0	JavaScript libraries
Google Analytics	Analytics
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
MailChimp	Marketing automation, Email
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
Popper	Miscellaneous
Site Kit 1.177.0	Analytics, WordPress plugins
DoubleClick Floodlight	Advertising
Underscore.js 1.13.7	JavaScript libraries
Priority Hints	Performance
WooCommerce	Ecommerce, WordPress plugins
WordPress 6.9.4	CMS, Blogs
WPForms	WordPress plugins, Form builders
reCAPTCHA	Security
Google Tag Manager	Tag managers
HSTS	Security
RSS	Miscellaneous
YouTube	Video players

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.twopinesmissoula.org/wp-json/	PHPSESSID	Set-Cookie: PHPSESSID=bcef4b2b9c3dd7d65f9e32834a321ace

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

URL	Cookie Name	Evidence
https://www.twopinesmissoula.org/wp-json/	PHPSESSID	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: PHPSESSID=bcef4b2b9c3dd7d65f9e32834a321ace

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

Software / Version	Category
All in One SEO 4.9.6.2	SEO, WordPress plugins
Animate.css	UI frameworks
Amazon Web Services	PaaS
Amazon S3	CDN
Bunny	CDN
Calendly	Appointment scheduling
Clipboard.js	JavaScript libraries
Elementor 4.0.4	Page builders, WordPress plugins
Font Awesome	Font scripts
jQuery Migrate 3.4.1	JavaScript libraries
Mailcheck 1.1.2	JavaScript libraries
punycode 1.0.0	JavaScript libraries
PubSubJS 3.4.0	JavaScript libraries
core-js 3.46.0	JavaScript libraries
Google Analytics	Analytics
jQuery 3.7.1	JavaScript libraries
jQuery UI 1.13.3	JavaScript libraries
MailChimp	Marketing automation, Email
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
Popper	Miscellaneous
Site Kit 1.177.0	Analytics, WordPress plugins
DoubleClick Floodlight	Advertising
Underscore.js 1.13.7	JavaScript libraries
Priority Hints	Performance
WooCommerce	Ecommerce, WordPress plugins
WordPress 6.9.4	CMS, Blogs
WPForms	WordPress plugins, Form builders
reCAPTCHA	Security
Google Tag Manager	Tag managers
HSTS	Security
RSS	Miscellaneous
YouTube	Video players

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.twopinesmissoula.org/	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(). 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. object-src: We recommend restricting object-src to 'none'. default-src: data: URI in default-src allows the execution of unsafe scripts. 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'.

https://www.twopinesmissoula.org/

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(). 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. object-src: We recommend restricting object-src to 'none'. default-src: data: URI in default-src allows the execution of unsafe scripts. 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'.

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

Evidence

URL	Method	Parameters	Evidence
https://www.twopinesmissoula.org/wp-json/wp/v2	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: PHPSESSID=bcef4b2b9c3dd7d65f9e32834a321ace	Possible API endpoint found at `/wp-json/wp/v2`

Vulnerability description

We found API endpoints while crawling the given web application.

Risk description

These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.

Recommendation

Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.

Evidence

URL	Method	Parameters	Evidence
https://www.twopinesmissoula.org/	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: info@twopinesmissoula.org

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 6.9.4	CMS, Blogs
MySQL	Databases
PHP	Programming languages
YouTube	Video players
Amazon Web Services	PaaS
WooCommerce	Ecommerce, WordPress plugins
Elementor 4.0.4	Page builders, WordPress plugins
All in One SEO Pack 4.9.6.2	SEO, WordPress plugins
All in One SEO 4.9.6.2	SEO, WordPress plugins
Site Kit 1.177.0	Analytics, WordPress plugins
reCAPTCHA	Security
punycode 1.0.0	JavaScript libraries
Mailcheck 1.1.2	JavaScript libraries
Calendly	Appointment scheduling
Amazon S3	CDN
Underscore.js 1.13.7	JavaScript libraries
MailChimp	Marketing automation, Email
jQuery Migrate 3.4.1	JavaScript libraries
jQuery	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics	Analytics
Font Awesome	Font scripts
DoubleClick Floodlight	Advertising
HSTS	Security
Bunny	CDN
Clipboard.js	JavaScript libraries

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
FreeBSD 11.0-RELEASE	85%

Evidence

Domain Queried	DNS Record Type	Description	Value
www.twopinesmissoula.org	A	IPv4 address	143.244.56.52
www.twopinesmissoula.org	AAAA	IPv6 address	2400:52e0:1e02::1217:1
www.twopinesmissoula.org	CNAME	Canonical name	twopinesmissoulaorg.b-cdn.net

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.