en
Severity across 5 analyzed records
A short verification protects source data and prevents automated AI requests.
The GCVE catalog currently lists 5 vulnerability records affecting HAPPY.
Among the 5 records analyzed by CyStack, 2 are High or Critical and 0 appear in the CISA KEV catalog.
Compare the version you run with each vulnerability and the provider guidance below. The data only includes records analyzed so far.
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
| CVE | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-39593WordPress HAPPY plugin <= 1.0.10 - Broken Access Control vulnerability | Exploitation statusNot known exploited | FixYes | Published05/21/2026 | SeverityMedium |
CVE-2025-67977WordPress HAPPY plugin <= 1.0.8 - Broken Access Control vulnerability | Exploitation statusNot known exploited | FixYes | Published02/20/2026 | SeverityHigh |
CVE-2025-68556WordPress HAPPY plugin <= 1.0.9 - Broken Access Control vulnerability | Exploitation statusNot known exploited | FixYes | Published12/23/2025 | SeverityMedium |
CVE-2025-49372WordPress HAPPY plugin <= 1.0.7 - Remote Code Execution (RCE) vulnerability | Exploitation statusNot known exploited | FixYes | Published11/06/2025 | SeverityCritical |
CVE-2025-53571WordPress HAPPY plugin <= 1.0.6 - Broken Access Control vulnerability | Exploitation statusNot known exploited | FixYes | Published09/05/2025 | SeverityMedium |
