CVE-2021-4380: Pinterest Automatic <= 4.14.3 - Unuathenticated Arbitrary Options Update
Noroxi assessment
Priority: Plan (action score 40/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB / GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.4% (FIRST EPSS); higher than 91.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The Pinterest Automatic plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on the 'wp_pinterest_automatic_parse_request' function and the 'process_form.php' script in versions up to, and including, 1.14.3. This makes it possible for unauthenticated attackers to update arbitrary options on a site that can be used to create new administrative user accounts or redirect unsuspecting site visitors.
- Published
- Jun 7, 2023
- Updated
- Jun 17, 2026
- EPSS
- 4.4% · 91th percentile
- CWE
- CWE-284
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · Wordfence
- 9.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Is Pinterest Automatic Pin on your site?
WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| valvepress | pinterest automatic pin | cpe:2.3:a:valvepress:pinterest_automatic_pin |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- valvepress pinterest automatic pinbefore 4.14.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Wordfence). Independent of NVD's CPE analysis and usually ahead of it.
ValvePress Pinterest Automatic
- up to and including 4.14.3affected · semver
Same product
valvepress: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-39510WordPress Pinterest Automatic Pin plugin < 4.19.0 - SQL Injection vulnerability34Monitor
- CVE-2025-39511WordPress Pinterest Automatic Pin plugin <= 4.19.0 - Broken Access Control Vulnerability17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Nuclei detection template ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2021-4380 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Jerome Bruandetfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.