Description
One or more pages contain possible sensitive information (e.g. a password parameter) and could be potentially cached. Even in secure SSL channels sensitive data could be stored by intermediary proxies and SSL terminators. To prevent this, a Cache-Control header should be specified.
Remediation
Prevent caching by adding "Cache Control: No-store" and "Pragma: no-cache" to the HTTP response header.
References
Related Vulnerabilities
WordPress Plugin Correos Woocommerce Arbitrary File Download (1.3.0.0)
WordPress Plugin Social Network Tabs Information Disclosure (1.7.1)
Plone CMS Exposure of Sensitive Information to an Unauthorized Actor Vulnerability (CVE-2013-4194)
WordPress Plugin Advanced Contact form 7 DB Information Disclosure (1.1.0)
WordPress Plugin Redux Framework Multiple Vulnerabilities (4.2.11)