How to fix: MooTools Detected
Outdated MooTools library detected.
Why it matters
Unmaintained library with potential security issues.
MooTools has limited maintenance.
How to fix it
- 1Migrate to a modern, maintained framework.
Code examples
Replace MooTools with modern browser APIs
// MooTools is abandoned, replace with modern equivalents:
// $("id") => document.getElementById("id")
// $$(".class") => document.querySelectorAll(".class")
// new Request({ url }).send() => fetch(url)
// new Element("div") => document.createElement("div")
// Array.each() => [].forEach()References
Detected automatically by VulnRadar. The check id is mootools-outdated, 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 MooTools Detected?
- VulnRadar rates this medium 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 mootools-outdated, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does MooTools Detected map to?
- It maps to CWE-1104. In the OWASP Top 10 it falls under A06:2021.
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.