Unauthorized state change via forged authenticated request
Published May 23, 2023 · Updated Apr 28, 2026
Cross-site request forgery in AboutMe3000 widget 2.2.6 and earlier allows remote attackers to trigger an unspecified state change. Patchstack has not disclosed the affected request handler, forged parameter, or server-side operation performed without request-origin validation. Exploitation requires an authorized WordPress account to interact with attacker-controlled content during an authenticated session; the resulting state change is not publicly identified.
Summary
What happened
Cross-site request forgery in AboutMe3000 widget 2.2.6 and earlier allows remote attackers to trigger an unspecified state change. Patchstack has not disclosed the affected request handler, forged parameter, or server-side operation performed without request-origin validation. Exploitation requires an authorized WordPress account to interact with attacker-controlled content during an authenticated session; the resulting state change is not publicly identified.
The record
- CVE
- CVE-2023-25474
- Published
- May 23, 2023
- Updated
- Apr 28, 2026
- Vendor
- Csaba Kissi
- Product
- About Me 3000 widget
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 23, 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 <=2.2.6
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