dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-4882

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The User Registration Advanced Fields plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'URAF_AJAX::method_upload' function in all versions up to, and including, 1.6.20. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. Note: The vulnerability can only be exploited if a "Profile Picture" field is added to the form.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The User Registration Advanced Fields WordPress plugin (versions up to 1.6.20) lacks file type validation in the URAF_AJAX::method_upload function, allowing unauthenticated attackers to upload arbitrary files. Exploitation requires a 'Profile Picture' field to exist in a registration form, and successful upload can lead to remote code execution.

MitigationUpdate the plugin to version 1.6.21 or later. If updates are unavailable, remove any 'Profile Picture' fields from registration forms and consider temporarily disabling the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of the User Registration Advanced Fields plugin
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'User Registration Advanced Fields' and note the version number displayed. Alternatively, check the plugin header in the main PHP file located in wp-content/plugins/user-registration-advanced-fields/
    Affected if The version is 1.6.20 or any earlier version
  2. Determine if any registration forms contain a Profile Picture field
    In WordPress admin, go to User Registration > Forms (or Form Builder). Review each form configuration to identify if a field type named 'Profile Picture' or similar image upload field has been added to any registration form.
    Affected if At least one registration form contains a Profile Picture or image upload field enabled for user registration
  3. Verify the file upload functionality is accessible
    Attempt to access the AJAX upload endpoint directly or review the site to confirm the registration form with Profile Picture field is publicly accessible. Check if the URAF_AJAX::method_upload function is reachable without authentication.
    Affected if The registration form with Profile Picture field is publicly accessible and the upload AJAX endpoint responds without requiring authentication
  4. Inspect server file upload configuration
    Review the wp-content/uploads/ directory permissions and check if the plugin stores uploaded files in a web-accessible location. Verify if any .php files or other executable files appear in the uploads folder that were not intentionally placed there.
    Affected if Uploaded files are stored in a web-accessible directory without execution prevention (e.g., no .htaccess restrictions)

You are affected if the User Registration Advanced Fields plugin version is 1.6.20 or earlier AND a Profile Picture field exists on a publicly accessible registration form, allowing unauthenticated users to potentially upload arbitrary executable files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.6.21 or later. If updates are unavailable, remove any 'Profile Picture' fields from registration forms and consider temporarily disabling the plugin.

Recommended fix Moderate confidence

User Registration Advanced Fields plugin version 1.6.21 or later

  1. 1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  2. 2. Locate the 'User Registration Advanced Fields' plugin
  3. 3. Check the current version installed (should be 1.6.20 or lower)
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update was successful by checking the plugin version after updating
  6. 6. Confirm that the 'Profile Picture' field functionality still works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4882 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4882 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data