dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25010

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in ILLID Share This Image share-this-image allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Share This Image: from n/a through <= 2.09.

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 · moderate confidence

This is a Missing Authorization vulnerability in the Share This Image WordPress plugin (versions <= 2.09). The plugin fails to properly enforce access control checks, allowing unauthenticated or unauthorized users to exploit incorrectly configured security levels to access or share images they should not have permission to view or manipulate.

MitigationImplement proper authorization verification checks before allowing image sharing or access operations. Validate user permissions against the requested resource and enforce role-based access control (RBAC) consistent with WordPress 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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. Verify the Share This Image plugin is installed
    Navigate to WordPress admin > Plugins and confirm 'Share This Image' appears in the installed plugins list
    Affected if The plugin is present and active in the WordPress installation
  2. Check the installed plugin version
    View the plugin details in the WordPress plugins admin page, or inspect the main plugin file header for the Version field
    Affected if The version number is 2.09 or lower
  3. Identify the security configuration settings
    Go to the plugin settings page in WordPress admin (usually under Settings or a dedicated menu item for 'Share This Image') and locate any options related to security levels, access restrictions, or permission controls
    Affected if Security level or access control settings are present and configurable in the plugin settings
  4. Verify if public/unauthenticated access is enabled
    Inspect the plugin configuration for settings that control who can view or share images - look for options labeled as public access, guest access, or authentication requirements
    Affected if The plugin allows unauthenticated users to access or share images through its security configuration

A user is affected if the Share This Image plugin (versions 2.09 or lower) is installed and active with security settings that permit unauthenticated or unauthorized access to restricted images.

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

Implement proper authorization verification checks before allowing image sharing or access operations. Validate user permissions against the requested resource and enforce role-based access control (RBAC) consistent with WordPress capabilities.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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