dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13386

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-25
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
The Social Images Widget plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'options_update' function in all versions up to, and including, 2.1. This makes it possible for unauthenticated attackers to delete the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Social Images Widget WordPress plugin has a missing capability check on the 'options_update' function, allowing unauthenticated attackers to delete plugin settings via a forged request. This is a Broken Access Control vulnerability (CWE-862) that requires social engineering to trick an administrator into clicking a malicious link.

MitigationUpdate to version 2.2 or later when available. In the interim, educate administrators about not clicking untrusted links and consider implementing CSRF protection as a defense-in-depth measure.

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 Social Images Widget plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Social Images Widget' in the list of installed plugins. Note its activation status.
    Affected if The plugin is installed and active on the WordPress site.
  2. Check installed version number
    In the WordPress admin under Plugins > Installed Plugins, find the Social Images Widget entry and locate the version number displayed below the plugin name. Compare this to version 2.2.
    Affected if The installed version is lower than 2.2 (the fixed version).
  3. Inspect the options_update function for capability checks
    Access the plugin source files via file manager or FTP. Locate the file containing the 'options_update' function (typically in the main plugin PHP file). Examine the function for the presence of a capability check such as 'current_user_can' or 'manage_options' before executing the options update logic.
    Affected if The options_update function lacks a capability check or only checks for a low-privilege capability that unauthenticated users could satisfy.
  4. Test for CSRF protection on options update action
    Attempt to submit a crafted request to the WordPress admin-post.php endpoint with the action parameter set to the plugin's options update action (if identifiable from the code). Observe whether the plugin validates a nonce or CSRF token.
    Affected if The plugin does not validate a nonce or CSRF token for the options_update action, allowing forged requests to succeed.

A user is affected if the Social Images Widget plugin is installed with a version lower than 2.2 and the options_update function either lacks capability checks or lacks CSRF protection, allowing unauthenticated settings deletion.

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 to version 2.2 or later when available. In the interim, educate administrators about not clicking untrusted links and consider implementing CSRF protection as a defense-in-depth measure.

Recommended fix Moderate confidence

Social Images Widget version 2.2 or higher

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Social Images Widget plugin
  4. Check if version 2.2 or higher is available in the WordPress plugin repository
  5. If version 2.2+ is available, click 'Update Now' to install the fixed version
  6. After updating, verify the plugin settings are preserved and functioning correctly
  7. Consider using a security plugin or web application firewall as an additional precaution against CSRF attacks

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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