← WordPress Vulnerabilities
WordPress security by component

Content No Cache: prevent specific content from being cached

Content No Cache: prevent specific content from being cached is a WordPress component with 1 published CVE record in this archive. The latest tracked vulnerability was published Dec 24, 2024; the highest published CVSS base score is 5.3.

Plugin slug: content-no-cache-prevent-specific-content-from-being-cached

CVE-2024-12103: Content No Cache: prevent specific content from being cached: A security weakness

Content No Cache: prevent specific content from being cached is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.

PublishedDec 24, 2024
Safe version guidanceSee mitigation notes
Published vulnerabilities for content-no-cache-prevent-specific-content-from-being-cached
Safe version
Dec 24, 2024 CVE-2024-12103
Content No Cache: prevent specific content from being cached: A security weakness
Content No Cache: prevent specific content from being cached is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
See mitigation notes
CVE5.3
NVDPending