dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-1730

HIGH · 8.8 CVSS v3.1 Published 2026-02-03
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

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 OS DataHub Maps plugin for WordPress is vulnerable to arbitrary file uploads due to incorrect file type validation in the 'OS_DataHub_Maps_Admin::add_file_and_ext' function in all versions up to, and including, 1.8.3. This makes it possible for authenticated attackers, with Author-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 OS DataHub Maps WordPress plugin fails to properly validate file types in the add_file_and_ext function, allowing authenticated users with Author-level permissions or higher to upload arbitrary files to the server, potentially achieving remote code execution.

MitigationUpdate the plugin to version 1.8.4 or later. Until an update is available, restrict or disable the file upload functionality for users below Administrator level.

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 if OS DataHub Maps plugin is installed
    Navigate to WordPress admin > Plugins and look for 'OS DataHub Maps' in the installed plugins list, or inspect the plugin directory at /wp-content/plugins/os-datahub-maps/
    Affected if The plugin is not found in the installed plugins list
  2. Determine the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the plugin name to view details, or read the 'readme.txt' or 'os-datahub-maps.php' file header in the plugin directory to find the Version field
    Affected if The version number is lower than 1.8.4 (e.g., 1.8.3, 1.8.2, etc.)
  3. Verify if non-administrator users have Author-level or higher access
    In WordPress admin > Users > All Users, review the role assigned to each user. Author role and above grants upload capabilities exploited by this vulnerability
    Affected if There are users with Author, Editor, or Contributor roles who have access to the WordPress admin area
  4. Check if the file upload feature is accessible
    Locate the add_file_and_ext function in the plugin files (typically in the main plugin PHP file or an includes file) and determine if the functionality is actively loaded for authorized user roles
    Affected if The file upload functionality is enabled and accessible to Author-level users (the function exists and is not disabled)
  5. Inspect the file upload validation logic
    Examine the add_file_and_ext function code for proper file type validation - look for allowlist validation of file extensions versus lack thereof
    Affected if The function does not properly validate or restrict file types to safe formats (images, documents) before allowing upload

A user is affected if the OS DataHub Maps plugin is installed with a version lower than 1.8.4 and non-administrator users with Author-level or higher permissions can access the file upload functionality.

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.8.4 or later. Until an update is available, restrict or disable the file upload functionality for users below Administrator level.

Recommended fix Moderate confidence

Version greater than 1.8.3 (check WordPress plugin repository for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the OS DataHub Maps plugin
  4. Click 'Update now' if an update is available, or manually upload the latest version from the WordPress plugin repository
  5. Verify the updated version is greater than 1.8.3
  6. Confirm the plugin is functioning correctly after 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-1730 — 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-1730 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