CVE-2021-4374 in the critical feed json
WordPress Automatic Plugin <= 3.53.2 - Unauthenticated Arbitrary Options Update
published 2023-06-07 3 y ago modified 2026-06-17 4 mo ago also EUVD-2021-34201
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.4%
- EPSS 16.4% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Metasploit, plus a Nuclei check
Summary
The WordPress Automatic Plugin for WordPress is vulnerable to arbitrary options updates in versions up to, and including, 3.53.2. This is due to missing authorization and option validation in the process_form.php file. This makes it possible for unauthenticated attackers to arbitrarily update the settings of a vulnerable site and ultimately compromise the entire site.
Patch / fix
- ValvePress WordPress Automatic Plugin 3.53.3
Timeline
- First public exploit (Metasploit auxiliary/admin/http/wp_automatic_plugin_privesc)
- Published
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 22 mo ago
Exploit prediction
16.41% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/admin/http/wp_automatic_plugin_privesc WordPress Plugin Automatic Config Change to RCE metasploit auxiliary, normal rank, 2021-09-06
- Nuclei template WordPress Automatic Plugin - Unauthenticated Options Change nuclei detection template
- blog.nintechnet.com https://blog.nintechnet.com/critical-vulnerability-fixed-in-wordpress-automatic-plugin/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- ValvePress WordPress Automatic Plugin
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
Sources
- CVE List CVE-2021-4374
- NVD CVE-2021-4374
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.