Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8622

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Image Sizes on Demand plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via PHP_SELF Server Variable in all versions up to, and including, 1.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The injected payload only executes in the context of an administrator, as the settings page requires the manage_options capability to render.

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

The Image Sizes on Demand WordPress plugin up to version 1.3 contains a reflected XSS vulnerability via the PHP_SELF server variable. The plugin fails to sanitize this input and escape output properly on its settings page, allowing unauthenticated attackers to inject malicious JavaScript through crafted URLs that execute when an administrator clicks the link.

MitigationUpdate to version 1.4 or later when available; in the interim, warn administrators against clicking untrusted links.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Image Sizes on Demand plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'image-sizes-on-demand' or similar, or query the wp_options table for the plugin active option.
    Affected if The plugin folder exists or the plugin is listed in WordPress active plugins.
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically image-sizes-on-demand.php) and locate the Version header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry.
    Affected if The version listed is 1.3 or lower (any version up to and including 1.3 is vulnerable).
  3. Confirm access to the plugin settings page
    Navigate to the WordPress admin settings page for this plugin (usually under Settings > Image Sizes or similar) and inspect the page source for the form action attribute.
    Affected if The page loads and contains a form that uses PHP_SELF in its action (look for $_SERVER['PHP_SELF'] or similar server variable in the HTML source).
  4. Verify the XSS vulnerability exists
    View the page source of the plugin settings page and search for unfiltered PHP_SELF or REQUEST_URI being output directly in HTML attributes without sanitization.
    Affected if The PHP_SELF value appears in the HTML without proper escaping (htmlspecialchars, esc_attr, etc.).

If the plugin is installed with version 1.3 or lower and the settings page renders PHP_SELF without sanitization, the environment is affected by this reflected XSS vulnerability.

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 1.4 or later when available; in the interim, warn administrators against clicking untrusted links.

Recommended fix Moderate confidence

Latest version after 1.3 (check wordpress.org/plugins/image-sizes-on-demand for current stable release)

  1. Upgrade the Image Sizes on Demand plugin to the latest available version from the WordPress plugin repository

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 / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-8622 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