dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-22630

CRITICAL · 9.9 CVSS v3.1 Published 2025-02-14
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 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
Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Marketing Fire Widget Options widget-options allows OS Command Injection.This issue affects Widget Options: from n/a through <= 4.1.0.

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 Widget Options plugin for WordPress (versions through 4.1.0) contains a command injection vulnerability where user-supplied input in widget options is not properly sanitized before being used in OS-level command execution. An attacker with administrative access or the ability to configure widgets could inject arbitrary OS commands via the plugin's options parameters.

MitigationUpdate Widget Options plugin to the latest version as soon as a patched release is available. If no update exists, disable the plugin immediately and review server access logs and user accounts for signs of compromise.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Confirm Widget Options plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Widget Options' in the installed plugins list, or check the /wp-content/plugins/widget-options directory exists on the server file system
    Affected if The plugin is present in the WordPress installation
  2. Identify installed version of Widget Options
    In WordPress admin > Plugins, click on the Widget Options plugin to view its details including version number, or inspect the main plugin file header comment for the Version field
    Affected if Version is 4.1.0 or lower (any version through 4.1.0)
  3. Verify plugin is active
    In WordPress admin > Plugins, check the status column for Widget Options - it will show 'Active' if currently enabled
    Affected if The plugin is active on the site
  4. Audit widget configurations for suspicious option values
    Navigate to Appearance > Widgets and review any widgets configured with Widget Options. Inspect each widget's settings panel for unexpected command strings, encoded payloads, or unusual option values that may indicate compromise
    Affected if Widget option values contain shell commands, suspicious encoded strings, or unexpected parameters

A system is affected if Widget Options plugin version 4.1.0 or lower is installed and active, allowing authenticated administrators to inject OS commands through plugin widget option parameters.

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 Widget Options plugin to the latest version as soon as a patched release is available. If no update exists, disable the plugin immediately and review server access logs and user accounts for signs of compromise.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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