dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-16236

HIGH · 8.8 CVSS v3.1 Published 2026-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 3 weeks old

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 Realtyna Organic IDX plugin for WordPress is vulnerable to Arbitrary File Upload in versions up to, and including, 5.3.0. This is due to missing file extension and content validation in the saveLiveImages() function combined with an insufficient authorization check on the get_keys() AJAX handler and a missing authentication check on the REST API import endpoint. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Realtyna Organic IDX WordPress plugin versions up to 5.3.0 contains an arbitrary file upload vulnerability. The issue stems from missing file extension and content-type validation in the saveLiveImages() function, combined with insufficient authorization checks on the get_keys() AJAX handler and a missing authentication requirement on the REST API import endpoint. This allows authenticated users with subscriber-level access or higher to upload arbitrary files to the server, potentially enabling remote code execution.

MitigationUpdate the Realtyna Organic IDX plugin to the latest version immediately. Until patched, restrict or disable file upload functionality and consider limiting subscriber-level user capabilities.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check the installed version of the Realtyna Organic IDX plugin
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Realtyna Organic IDX' to see the current version number. Alternatively, check the plugin header in wp-content/plugins/realtyna-organic-idx/index.php
    Affected if The installed version is 5.3.0 or lower (any version up to and including 5.3.0)
  2. Verify the saveLiveImages function is accessible
    Check if the WordPress AJAX handler for 'realtyna_save_live_images' or similar is registered and accessible. This can be confirmed by examining the plugin files for the saveLiveImages function and testing if the corresponding AJAX endpoint responds.
    Affected if The saveLiveImages function exists and handles file uploads without proper extension or content-type validation
  3. Confirm the get_keys AJAX handler authorization
    Test the AJAX endpoint for get_keys functionality by making a request as a subscriber-level user. In WordPress, check the capability check in the AJAX handler callback - it should require more than 'read' capability.
    Affected if The get_keys AJAX handler accepts requests from users with subscriber-level privileges (capability level 'read' or below)
  4. Check REST API import endpoint authentication
    Examine the plugin's REST API routes, particularly any import-related endpoints. Test making a request to the import endpoint without providing authentication credentials.
    Affected if The REST API import endpoint allows unauthenticated access (no nonce or authentication token required)
  5. Confirm the plugin is active on the WordPress site
    List all active plugins in WordPress admin under Plugins > Installed Plugins, or query the wp_options table for the active_plugins option
    Affected if The Realtyna Organic IDX plugin is installed and activated

The environment is affected if the Realtyna Organic IDX plugin version is 5.3.0 or lower, the plugin is active, and the vulnerable endpoints (saveLiveImages AJAX, get_keys AJAX, or REST API import) are accessible without proper authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Realtyna Organic IDX plugin to the latest version immediately. Until patched, restrict or disable file upload functionality and consider limiting subscriber-level user capabilities.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-16236 — 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-16236 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