Vulnerability Scan Result

Target:

https://www.drnason.com/

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

Submitted: May 12, 2026 from ST

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Keller Dentists \| Leslie Nason, DDS
Description:	Leslie Nason, DDS is a comprehensive dentist in Keller, TX. We support your dental health in a relaxing environment. Call us to schedule a visit.

IP Information

ip_address	199.46.34.124
country	US
network_name	Akamai International B.V.
asn	AS213120

Open Ports

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

Web Technologies

Software / Version	Category
Birdeye	Marketing automation, Widgets
parallax.js	JavaScript libraries
Google Analytics	Analytics
MySQL	Databases
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
DoubleClick Floodlight	Advertising
WordPress	CMS, Blogs
Google Tag Manager	Tag managers
HSTS	Security
Scorpion	CMS

Web Application Vulnerabilities

Evidence

URL Evidence

URL	Evidence
https://www.drnason.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: script-src should not allow '' as source. This may enable execution of malicious JavaScript. script-src: data: URI in script-src allows the execution of unsafe scripts. object-src: We recommend restricting object-src to 'none'. 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-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. default-src: data: URI in default-src allows the execution of unsafe scripts. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().

https://www.drnason.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: script-src should not allow '*' as source. This may enable execution of malicious JavaScript. script-src: data: URI in script-src allows the execution of unsafe scripts. object-src: We recommend restricting object-src to 'none'. 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-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. default-src: data: URI in default-src allows the execution of unsafe scripts. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().

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

Software / Version	Category
Birdeye	Marketing automation, Widgets
parallax.js	JavaScript libraries
Google Analytics	Analytics
MySQL	Databases
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
DoubleClick Floodlight	Advertising
WordPress	CMS, Blogs
Google Tag Manager	Tag managers
HSTS	Security
Scorpion	CMS

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
https://www.drnason.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	Summary
https://www.drnason.com/	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: OPTIONS, TRACE, GET, HEAD, POST` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

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

Operating System	Accuracy
Linux 4.0	85%

Evidence

Software / Version	Category
Scorpion	CMS
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Nginx	Web servers, Reverse proxies
parallax.js	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics	Analytics
Birdeye	Marketing automation, Widgets
DoubleClick Floodlight	Advertising
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.

Evidence

Domain Queried	DNS Record Type	Description	Value
www.drnason.com	A	IPv4 address	199.46.34.124
www.drnason.com	CNAME	Canonical name	he005.scorphosting.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.