Vulnerability Scan Result

Target:

http://www.getdmvapt.com/ (redirect)

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

Submitted: Mar 22, 2026 from GH

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Texas DPS Appointment Booking Service \| Get DMV Appointments \| Get DMV Appointments
Description:	Skip the 4-month wait for your Texas DPS appointment. Our automated system monitors every DPS office 24/7 and books your driver license appointment in days, not months. Texas DMV appointment scheduling made easy.

IP Information

ip_address	216.150.1.129
country	US
network_name	Amazon.com, Inc.
asn	AS16509

ip_address	216.150.16.129
country	US
network_name	Amazon.com, Inc.
asn	AS16509

Open Ports

80/tcp	http	Vercel -
443/tcp	https	Vercel -

Web Technologies

Software / Version	Category
Apple Sign-in	Authentication
Lucide	Font scripts
Next.js 14.2.35	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Open Graph	Miscellaneous
React	JavaScript frameworks
Vercel	PaaS
Webpack	Miscellaneous
Priority Hints	Performance
Radix UI	UI frameworks
HSTS	Security

Web Application Vulnerabilities

Evidence

URL
https://www.getdmvapt.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.getdmvapt.com/signup	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	The following form sends inputs of type password plainly in the URL: ` Full name * Email address * <label for=":Raujsvafcq:" ... (truncated)

Vulnerability description

We found a form which is submitted using a GET method and has inputs of the type password. The end result is that passwords are submitted in URLs.

Risk description

Passwords submitted in URLs have a higher chance of being leaked. The main reason is that URLs can be leaked in browser cross-site requests via the Referer header. Additionally, URLs are usually stored in all kinds of logs. If any access or error logs of the server were publicly accessible, an attacker could also harvest password from it.

Recommendation

You should submit passwords using POST rather than GET. This way sensitive data won't be shared to other locations via URLs.

Classification

CWE	CWE-598
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Apple Sign-in	Authentication
Lucide	Font scripts
Next.js 14.2.35	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Open Graph	Miscellaneous
React	JavaScript frameworks
Vercel	PaaS
Webpack	Miscellaneous
Priority Hints	Performance
Radix UI	UI frameworks
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.

Classification

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

Evidence

URL Evidence

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

https://www.getdmvapt.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: We recommend restricting object-src to 'none'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. 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. 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

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

Evidence

URL Evidence

URL	Evidence
https://www.getdmvapt.com/signup	<input id=":Rmjsvafcq:" aria-required="true" class="h-12 w-full rounded-md bg-bg-input px-3.5 py-3 text-base text-text placeholder:text-text-placeholder border border-border outline-none transition-[border-color,box-shadow] duration-200 ease-out hover:border-border-light focus:border-border-focus focus:shadow-focus disabled:cursor-not-allowed disabled:opacity-50 disabled:bg-bg-raised" type="email" placeholder="you@example.com" autocomplete="email" name="email"> <input id=":Raujsvafcq:" aria-required="true" class="h-12 w-full rounded-md bg-bg-input px-3.5 py-3 text-base text-text placeholder:text-text-placeholder border border-border outline-none transition-[border-color,box-shadow] duration-200 ease-out hover:border-border-light focus:border-border-focus focus:shadow-focus disabled:cursor-not-allowed disabled:opacity-50 disabled:bg-bg-raised" type="password" placeholder="Create a password" autocomplete="new-password" name="password"> <button class="relative inline-flex items-center justify-center rounded-full font-medium transition-all duration-100 ease-out-custom active:scale-[0.98] focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-accent disabled:opacity-40 disabled:cursor-not-allowed disabled:pointer-events-none bg-accent text-white border-0 hover:opacity-90 h-[52px] px-10 text-base min-w-[120px] mt-6 w-full" type="submit"><span class="inline-flex items-center justify-center">Create Account</span></button>

https://www.getdmvapt.com/signup

<input id=":Rmjsvafcq:" aria-required="true" class="h-12 w-full rounded-md bg-bg-input px-3.5 py-3 text-base text-text placeholder:text-text-placeholder border border-border outline-none transition-[border-color,box-shadow] duration-200 ease-out hover:border-border-light focus:border-border-focus focus:shadow-focus disabled:cursor-not-allowed disabled:opacity-50 disabled:bg-bg-raised" type="email" placeholder="you@example.com" autocomplete="email" name="email"> <input id=":Raujsvafcq:" aria-required="true" class="h-12 w-full rounded-md bg-bg-input px-3.5 py-3 text-base text-text placeholder:text-text-placeholder border border-border outline-none transition-[border-color,box-shadow] duration-200 ease-out hover:border-border-light focus:border-border-focus focus:shadow-focus disabled:cursor-not-allowed disabled:opacity-50 disabled:bg-bg-raised" type="password" placeholder="Create a password" autocomplete="new-password" name="password"> <button class="relative inline-flex items-center justify-center rounded-full font-medium transition-all duration-100 ease-out-custom active:scale-[0.98] focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-accent disabled:opacity-40 disabled:cursor-not-allowed disabled:pointer-events-none bg-accent text-white border-0 hover:opacity-90 h-[52px] px-10 text-base min-w-[120px] mt-6 w-full" type="submit"><span class="inline-flex items-center justify-center">Create Account</span></button>

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

Risk description

The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.

Recommendation

Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.

Classification

CWE	CWE-287
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://www.getdmvapt.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	Email Address: hello@getdmvapt.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

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Vercel	PaaS
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.getdmvapt.com	A	IPv4 address	216.150.1.193
www.getdmvapt.com	A	IPv4 address	216.150.16.193
www.getdmvapt.com	CAA	Certificate Authority Authorization	0 issue "globalsign.com"
www.getdmvapt.com	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
www.getdmvapt.com	CAA	Certificate Authority Authorization	0 issue "pki.goog"
www.getdmvapt.com	CAA	Certificate Authority Authorization	0 issue "sectigo.com"
www.getdmvapt.com	CNAME	Canonical name	70b03b85002e98b8.vercel-dns-016.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.