Request forgery via REST request handling
Published Oct 8, 2026 · Updated Oct 8, 2026
CSRF in REST request handling in Melapress WP 2FA 4.1.0 and earlier allows remote attackers to forge requests through a victim's browser. Melapress identifies REST request handling as the affected component but does not disclose the faulty check or affected action. Exploitation requires user interaction; the available disclosure does not identify the required victim role or the specific resulting changes.
Summary
What happened
CSRF in REST request handling in Melapress WP 2FA 4.1.0 and earlier allows remote attackers to forge requests through a victim's browser. Melapress identifies REST request handling as the affected component but does not disclose the faulty check or affected action. Exploitation requires user interaction; the available disclosure does not identify the required victim role or the specific resulting changes.
The record
- CVE
- CVE-2026-62142
- Published
- Oct 8, 2026
- Updated
- Oct 8, 2026
- Vendor
- Melapress
- Product
- WP 2FA
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 8, 2026CVE publishedPublication date reported by the CVE source.
- Oct 8, 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 <=4.1.0 changes=[{"at":"4.2.0","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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started