Loading vulnerability…
CVE-2026-4882 is an arbitrary file upload vulnerability in the User Registration Advanced Fields plugin for WordPress affecting all versions up to and including 1.6.20. The flaw is caused by missing file type validation in the URAF_AJAX::method_upload function. When the vulnerable upload path is reachable, an unauthenticated attacker can submit a crafted upload request and place arbitrary files on the server. The issue is only exploitable when a Profile Picture field has been added to the relevant form. Because the uploaded content can include server-executable code, the vulnerability may be leveraged to achieve remote code execution on the affected WordPress site.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a compact exploit package for CVE-2026-4882 affecting the WordPress User Registration Advanced Fields plugin <= 1.6.20. It contains three files: a README describing the vulnerability and usage, a Python exploit script (shadow.py), and a PHP payload (shadow.php). The exploit is not part of a larger framework. The main capability is unauthenticated arbitrary file upload leading to remote code execution. The Python script automates target discovery and exploitation by scanning likely registration-related paths, crawling the homepage and sitemap.xml for additional paths, extracting the leaked uraf_profile_picture_upload_nonce and candidate form IDs from HTML, and then attempting upload through the vulnerable profile-picture AJAX workflow while using the documented is_snapshot=1 bypass. It supports single-target, mass-target, and interactive modes, uses multithreading, handles redirects, and saves successful shell URLs to shell.txt. The payload is operational rather than just demonstrative: shadow.php is a GIF89a/PHP polyglot webshell intended to survive superficial image checks. Once uploaded into wp-content/uploads/user_registration_uploads/temp-uploads/, it provides a simple file-upload interface that can be used to place additional attacker-controlled files on the server. That gives the attacker a persistent foothold and practical RCE capability through server-side PHP execution. Repository structure is straightforward: README.md documents the vulnerability and command-line usage; shadow.py is the primary exploit entry point and contains scanning, nonce/form discovery, upload logic, concurrency, and result logging; shadow.php is the malicious uploaded shell. Overall, this is a real offensive exploit repository designed to automate exploitation of vulnerable WordPress sites at scale, not merely detect exposure.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An arbitrary file upload vulnerability in User Registration Advanced Fields listed among the actor's initial access tooling.
An arbitrary file upload vulnerability in the User Registration Advanced Fields plugin for WordPress caused by missing file type validation in the URAF_AJAX::method_upload function, affecting all versions through 1.6.20 and potentially enabling remote code execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.