Unauthenticated comment deletion via unchecked AJAX identifier
Published Sep 20, 2026 · Updated Sep 20, 2026
Missing authorization in Refresh Themes Tripzzy before 1.5.1 allows remote attackers to permanently delete arbitrary site comments. An unauthenticated WordPress AJAX action removes the object named by a supplied identifier without validating that identifier or checking authorization. Network access to an affected WordPress site is sufficient, and the consequence is irreversible loss of selected comment content.
Summary
What happened
Missing authorization in Refresh Themes Tripzzy before 1.5.1 allows remote attackers to permanently delete arbitrary site comments. An unauthenticated WordPress AJAX action removes the object named by a supplied identifier without validating that identifier or checking authorization. Network access to an affected WordPress site is sufficient, and the consequence is irreversible loss of selected comment content.
The record
- CVE
- CVE-2026-87839
- Published
- Sep 20, 2026
- Updated
- Sep 20, 2026
- Vendor
- Refresh Themes
- Product
- Tripzzy
- Classifications
- CWE-284, T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2026CVE publishedPublication date reported by the CVE source.
- Sep 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.1.8 <1.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started