Settings alteration via missing CSRF validation
Published May 15, 2025 · Updated May 17, 2025
CSRF in Simple Nav Archives 2.1.3 and earlier allows remote attackers to alter plugin settings through an administrator's browser. The wp-admin plugin settings handler accepts a cross-origin POST containing archive display and wrapper fields without validating a CSRF token. Exploitation requires a logged-in administrator to open attacker-controlled HTML, and the demonstrated consequence is unauthorized modification of archive presentation settings.
Summary
What happened
CSRF in Simple Nav Archives 2.1.3 and earlier allows remote attackers to alter plugin settings through an administrator's browser. The wp-admin plugin settings handler accepts a cross-origin POST containing archive display and wrapper fields without validating a CSRF token. Exploitation requires a logged-in administrator to open attacker-controlled HTML, and the demonstrated consequence is unauthorized modification of archive presentation settings.
The record
- CVE
- CVE-2024-8398
- Published
- May 15, 2025
- Updated
- May 17, 2025
- Vendor
- Philip Walton
- Product
- Simple Nav Archives
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2025CVE publishedPublication date reported by the CVE source.
- May 17, 2025Record 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 <=2.1.3
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
- WPScan cross-origin settings-update proof of conceptproof of concept · demonstrated
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