Unspecified action via forged cross-site request
Published Oct 16, 2023 · Updated Apr 28, 2026
Cross-site request forgery in Pixelative AMP WP – Google AMP For WordPress 1.5.15 and earlier allows remote attackers to trigger an unspecified action. The CNA and its sole referenced advisory do not identify the affected handler or the state-changing operation that accepts a forged request. Exploitation requires user interaction; the victim's authentication state or role and the resulting integrity or availability effect remain undisclosed.
Summary
What happened
Cross-site request forgery in Pixelative AMP WP – Google AMP For WordPress 1.5.15 and earlier allows remote attackers to trigger an unspecified action. The CNA and its sole referenced advisory do not identify the affected handler or the state-changing operation that accepts a forged request. Exploitation requires user interaction; the victim's authentication state or role and the resulting integrity or availability effect remain undisclosed.
The record
- CVE
- CVE-2023-45831
- Published
- Oct 16, 2023
- Updated
- Apr 28, 2026
- Vendor
- Pixelative
- Product
- AMP WP – Google AMP For WordPress
- Classifications
- CWE-352, CAPEC-62, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2023CVE 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=n/a <=1.5.15
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