CVE-2026-39473
Sensitive Data Exposure in Simple History Plugin
Publication date: 2026-04-08
Last updated on: 2026-04-13
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| par_thernström | simple_history | From 5.0.0 (inc) to 5.24.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-201 | The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in the Simple History plugin allows unauthenticated attackers to access sensitive information that is normally restricted. This exposure of sensitive data can lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access.
Although the CVSS score indicates a low severity impact, the ability to retrieve embedded sensitive data can increase the risk of data breaches, potentially resulting in regulatory penalties and loss of trust.
Users are advised to update to version 5.24.1 or later to mitigate this risk and help maintain compliance with relevant data protection standards.
Can you explain this vulnerability to me?
CVE-2026-39473 is a vulnerability in the WordPress Simple History Plugin versions up to and including 5.24.0 that allows unauthenticated attackers to access sensitive information that should normally be restricted.
This issue is classified as Sensitive Data Exposure and falls under the OWASP Top 10 category A3. It enables attackers to retrieve embedded sensitive data without any privileges.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized disclosure of sensitive information, which may allow attackers to exploit other system weaknesses.
Because it requires no authentication, attackers can easily exploit this vulnerability, potentially affecting many websites regardless of their traffic or popularity.
The CVSS score of 5.3 indicates a low severity impact, but the exposure of sensitive data can still have serious consequences depending on the nature of the data.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability CVE-2026-39473 in the WordPress Simple History Plugin, you should update the plugin to version 5.24.1 or later, where the issue has been patched.
Additionally, consider enabling auto-updates for the plugin if your platform supports it, to ensure you receive future security patches promptly.