CVE-2026-1294
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 · uneditedThe All In One Image Viewer Block plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.0.2 due to missing authorization and URL validation on the image-proxy REST API endpoint. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 confidenceThe All In One Image Viewer Block plugin for WordPress versions up to 1.0.2 contains an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in its image-proxy REST API endpoint. The endpoint lacks both authorization checks and URL validation, allowing attackers to instruct the server to make arbitrary HTTP requests to internal or external 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the plugin is installedNavigate to WordPress admin > Plugins and look for 'All In One Image Viewer Block' or check the /wp-content/plugins/ directory for a folder containing 'all-in-one-image-viewer' or similar namingAffected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed versionCheck the plugin's main PHP file header for the 'Version' comment, or view the plugin in WordPress admin which displays the version numberAffected if The displayed version is 1.0.2 or any version lower than 1.0.2
-
Locate the vulnerable REST API endpointExamine the plugin's PHP files for REST API route registration (typically using register_rest_route) and look for routes related to 'image-proxy' or 'proxy' functionalityAffected if A REST API endpoint handling image proxy requests is registered by the plugin
-
Test unauthenticated access to the endpointUsing a tool like curl, send a GET request to the REST API endpoint (such as /wp-json/aiiov/image-proxy or similar path found in step 3) without providing any authentication credentialsAffected if The endpoint responds without requiring authentication (no 401 or 403 error)
-
Verify URL validation is missingInspect the PHP code handling the REST API request to see if it validates or restricts the URLs being requested (look for whitelist validation, hostname filtering, or allowlist logic)Affected if The code directly uses user-supplied URLs in file retrieval functions without validation checks
If the plugin is installed with version 1.0.2 or lower and the image-proxy REST API endpoint is accessible without authentication, the environment is affected by this SSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to the latest patched version once available. Until then, consider disabling the plugin or restricting REST API access at the server level (e.g., via .htaccess or firewall rules) to prevent unauthenticated access to the vulnerable endpoint.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1294 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1294 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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