dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-23803

MEDIUM · 6.4 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
Server-Side Request Forgery (SSRF) vulnerability in Burhan Nasir Smart Auto Upload Images smart-auto-upload-images allows Server Side Request Forgery.This issue affects Smart Auto Upload Images: from n/a through <= 1.2.2.

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

Server-Side Request Forgery (SSRF) vulnerability in the Smart Auto Upload Images WordPress plugin allows remote attackers to induce the server to make arbitrary HTTP requests to internal or external resources by manipulating input parameters used in image upload/fetching functionality.

MitigationRestrict the plugin's ability to make outbound requests by implementing strict URL allow-listing, validating that all requested URLs point to trusted domains, and disabling the ability to access internal network resources.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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. Identify if the Smart Auto Upload Images plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Smart Auto Upload Images' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'smart-auto-upload-images' and examine the main plugin file header for the version number.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, click on the plugin to view details, or open the main plugin PHP file (usually smart-auto-upload-images.php) and locate the Version header in the plugin comments. Compare this version against any official vulnerability advisory.
    Affected if The installed version is lower than the patched version (if known) or is an unpatched release
  3. Verify if the auto-upload functionality is enabled
    Navigate to the plugin settings page in WordPress admin (usually under Settings > Smart Auto Upload or a similar menu item). Check whether the automatic image fetching/upload feature is turned on, and inspect any configuration options that control which URLs can be fetched or uploaded.
    Affected if The auto-upload feature is enabled and accessible to users or unauthenticated attackers
  4. Review server access and error logs for suspicious outbound requests
    Examine Apache/nginx access logs and WordPress debug logs for unusual HTTP requests originating from the server. Look for requests to internal IP addresses (127.0.0.1, 10.x.x.x, 192.168.x.x), cloud metadata endpoints (169.254.169.254), or unexpected external domains that coincide with plugin usage.
    Affected if Outbound HTTP requests to internal resources or unexpected external domains are present in logs around the time of plugin activity
  5. Inspect for SSRF indicators in WordPress audit logs
    If audit logging is enabled, search for entries related to the plugin's upload/fetch actions. Check for any instances where the plugin made requests to internal network resources, localhost, or non-standard ports that were not intended by administrators.
    Affected if Audit logs show the plugin making requests to internal IPs, cloud metadata services, or unauthorized external domains

The environment is affected if the Smart Auto Upload Images plugin is installed with its image fetch/upload functionality enabled, allowing an attacker to coerce the server into making arbitrary HTTP requests to internal or external resources via the plugin's input 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

Restrict the plugin's ability to make outbound requests by implementing strict URL allow-listing, validating that all requested URLs point to trusted domains, and disabling the ability to access internal network resources.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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