Content No Cache: prevent specific content from being cached <= 0.1.2 - Unauthenticated Private Content Disclosure

5.3
Authorization Bypass Through User-Controlled Key
CVE CVE-2024-12103
CVSS 5.3 (Medium)
Publicly Published December 23, 2024
Last Updated December 24, 2024
Researcher Francesco Carlucci

Description

The Content No Cache: prevent specific content from being cached plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 0.1.2 via the eos_dyn_get_content action due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to.

References

Share

Vulnerability Details for Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.

Software Type Plugin
Software Slug content-no-cache (view on wordpress.org)
Patched? Yes
Remediation Update to version 0.1.3, or a newer patched version
Affected Version
  • <= 0.1.2
Patched Version
  • 0.1.3

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation