Unspecified state change via forged requests
Published May 16, 2025 · Updated Apr 28, 2026
Cross-site request forgery in Javier Revilla ValidateCertify Free 1.6.4 and earlier allows remote attackers to cause an unspecified action. Neither Patchstack nor the plugin changelog identifies the affected request handler or the state-changing operation accepted without CSRF validation. Exploitation requires a WordPress user to interact with attacker-controlled content, and the published impact is limited to an unspecified integrity change.
Summary
What happened
Cross-site request forgery in Javier Revilla ValidateCertify Free 1.6.4 and earlier allows remote attackers to cause an unspecified action. Neither Patchstack nor the plugin changelog identifies the affected request handler or the state-changing operation accepted without CSRF validation. Exploitation requires a WordPress user to interact with attacker-controlled content, and the published impact is limited to an unspecified integrity change.
The record
- CVE
- CVE-2025-48115
- Published
- May 16, 2025
- Updated
- Apr 28, 2026
- Vendor
- Javier Revilla
- Product
- ValidateCertify Free
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=0 <=1.6.4 changes=[{"at":"1.6.5","status":"unaffected"}]
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.
Weakness, pattern, technique
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo