How to fix: jQuery cookie plugin usage
jQuery.cookie() sets cookies via JS and bypasses HttpOnly-equivalent protections.
Why it matters
Use the server's Set-Cookie header instead
jQuery.cookie() sets cookies via JS and bypasses HttpOnly-equivalent protections.
How to fix it
- 1Use the server's Set-Cookie header instead
Code examples
Set cookies with Secure and HttpOnly via server
// BAD: JavaScript can only set cookies without HttpOnly
// $.cookie("session", token, { secure: true });
// This CANNOT set HttpOnly, XSS can still steal it
// GOOD: set session cookies server-side only
res.setHeader("Set-Cookie",
`session=${token}; HttpOnly; Secure; SameSite=Strict; Path=/`
);
// Server-set cookies with HttpOnly cannot be read by JSReferences
Detected automatically by VulnRadar. The check id is code-cookie-write-via-jquery, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is jQuery cookie plugin usage?
- VulnRadar rates this low severity in the code 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 code-cookie-write-via-jquery, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does jQuery cookie plugin usage map to?
- It maps to CWE-614. In the OWASP Top 10 it falls under A05: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.