Skip to main content
MediumHeadersOWASP A04:2021CWE-525

How to fix: Sensitive Page Missing no-store

Page with credentials lacks Cache-Control: no-store.

Why it matters

Sensitive data may be cached.

no-store prevents all caching.

How to fix it

  1. 1Add Cache-Control: no-store to sensitive pages.

Code examples

Add Cache-Control: no-store for sensitive pages

JavaScript
// Prevent browsers and proxies from caching sensitive responses
export default {
  async headers() {
    return [
      // Apply to dashboard and account pages only:
      { source: "/(dashboard|account|admin)(.*)", headers: [{
        key: "Cache-Control",
        value: "no-store, max-age=0"
      }]}
    ];
  },
};

References

Detected automatically by VulnRadar. The check id is cache-control-no-store-missing, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Sensitive Page Missing no-store?
VulnRadar rates this medium severity in the headers 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 cache-control-no-store-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Sensitive Page Missing no-store map to?
It maps to CWE-525. In the OWASP Top 10 it falls under A04: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.

Propose a checkHow a check is built

Scan your own site for sensitive page missing no-store

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Sensitive Page Missing no-store | VulnRadar