How to fix: Form action uses tel: scheme
A <form action="tel:..."> opens the device's phone dialer instead of submitting data anywhere, which is usually a mistake for a form that has input fields.
Why it matters
Not itself an injection vector, but a tel: action silently discards any form data instead of submitting it, which can hide a broken contact/callback form from users.
A <form action="tel:..."> triggers the device dialer on submit. It's usually intended for a plain "call us" link, not an actual form with fields, and should be a <a href="tel:..."> instead.
How to fix it
- 1Use a plain <a href="tel:+1..."> link for click-to-call instead of wrapping it in a <form>.
- 2If the form collects data, point action at a real endpoint and trigger the call separately.
Code examples
Use a tel: link instead of a tel: form action
<!-- BAD: form data is discarded, only the dialer opens -->
<!-- <form action="tel:+15551234567"><input name="note"><button>Call</button></form> -->
<!-- GOOD: click-to-call as a link -->
<a href="tel:+15551234567">Call us</a>
<!-- If you need to submit data, use a real endpoint -->
<form action="/api/callback-request" method="post">...</form>References
Detected automatically by VulnRadar. The check id is form-action-tel-scheme, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Form action uses tel: scheme?
- VulnRadar rates this low severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id form-action-tel-scheme, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.