Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege WordPress user
-
ExploitSend request to unprotected plugin endpoint
-
ExecutionBypass missing authorization check
-
ImpactRead or modify plugin data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the vulnerable 'Before After Image Comparison - Image comparison for WP' plugin (version n/a through 1.1.21) installed and active on a WordPress site, plus an authenticated account at a low privilege level (PR:L per the CVSS vector) - a self-registration-enabled site or any multi-user/membership deployment provides the needed foothold. The limiting factor is the authentication requirement: fully unauthenticated visitors cannot exploit it, so single-administrator sites with no untrusted registered users face minimal realistic exposure. No user interaction is required (UI:N), and impact is bounded to partial confidentiality and integrity of plugin-controlled data (C:L/I:L, no availability impact). |
| Impact | This is a medium-severity (CVSS 5.4) broken access control / missing authorization flaw (CWE-862) in the bPlugins 'Before After Image Comparison' WordPress plugin, affecting all versions up to and including 1.1.21. The provided CVSS vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) indicates network-reachable, low-complexity exploitation requiring an authenticated low-privilege account (PR:L), with only partial confidentiality and integrity impact and no availability impact - consistent with a subscriber- or contributor-level user reaching plugin functions gated by improperly configured access-control checks. No EPSS score, CISA KEV listing, or public POC was supplied in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The signals are internally consistent (no CVSS-versus-description conflict), and the modest impact plus the authentication requirement place this as a routine patch-management item rather than an emergency: real priority is moderate - elevate for multi-author or membership WordPress sites where low-privilege accounts are untrusted, deprioritize for single-admin sites. EPSS is absent (not low), so widespread automated exploitation cannot be inferred either way. |
| Exploit ScenarioDerived | An attacker who holds any low-privilege authenticated account (e.g., subscriber or contributor) on a WordPress site running the vulnerable plugin sends a request to a plugin action or endpoint that fails to verify the caller's authorization. Because the access-control check is missing or misconfigured, the attacker reads or modifies plugin-managed data they should not reach. No public exploit code was identified in the provided data, and the low attack complexity (AC:L) means no special timing or conditions are needed once a foothold account exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Authenticated low-privilege users on WordPress sites running the bPlugins 'Before After Image Comparison - Image comparison for WP' plugin (all versions through 1.1.21) can reach plugin functionality that lacks proper authorization checks, allowing them to read and alter data the plugin is intended to restrict (CWE-862, CVSS 5.4). The defect is remotely reachable over the network with no user interaction (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N), so any site that allows self-registration or hosts multiple untrusted accounts provides the necessary foothold, while single-administrator sites with no untrusted users face minimal realistic exposure. No public exploit code was identified at time of analysis and there is no confirmed active exploitation, but the low privilege prerequisite and network reachability make the prerequisite account easy to obtain on open-registration deployments.
RemediationAI
No fixed version is specified in the available data and the supplied reference set contains only the Patchstack advisory, so patch status is not confirmed at time of analysis; treat the vendor advisory at https://patchstack.com/database/wordpress/plugin/before-after-image-compare/vulnerability/wordpress-before-after-image-comparison-image-comparison-for-wp-plugin-1-1-21-broken-access-control-vulnerability?_s_id=cve and the WordPress plugin repository changelog as the sources of truth, and upgrade to the first release published after 1.1.21 as soon as it is available. If no update can be applied, the most effective compensating control is to deactivate or uninstall the plugin - the trade-off is the loss of the image-comparison functionality. Where the plugin must remain active, harden the prerequisite: disable open user registration and remove or downgrade unused low-privilege accounts so the PR:L foothold is not freely obtainable, and audit subscriber/contributor accounts for anything untrusted (side effect: onboarding friction for legitimate members). Additionally, deploy virtual patching at the WAF layer to require authenticated, capability-checked access to the plugin's AJAX and REST endpoints, or block direct requests to the plugin's namespace from non-administrator sessions; this will not break legitimate admin usage but must be tuned to avoid blocking authenticated front-end features, and it is a temporary mitigation until a vendor patch is installed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerable component is a WordPress plugin distributed through the WordPress plugin ecosystem by bPlugins; the supplied CPE (cpe:2.3:a:bplugins:before_after_image_comparison_-_image_comparison_for_wp:*:*:*:*:*:*:*:*) identifies the vendor/product pair but carries no version constraint, so version scoping comes from the advisory text (through 1.1.21). The root cause class is CWE-862 Missing Authorization, reported by Patchstack as a broken access control issue: WordPress plugins typically expose privileged operations through admin-ajax.php actions, admin-post.php handlers, REST API routes, or settings-update functions, and these handlers are only as safe as the capability checks (current_user_can) and nonce/token validations they perform. When those checks are absent or incorrectly configured, any authenticated user - including a subscriber-level account - can invoke the handler and act beyond their intended role. Because the CVSS vector is network-reachable with PR:L rather than PR:N, the missing check is not a fully unauthenticated bypass; it is a horizontal/vertical privilege escalation bounded to partial confidentiality and integrity impact (C:L/I:L) with no availability impact (A:N) and no scope change (S:U), consistent with a plugin-scoped access control failure rather than a site-wide compromise.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Missing authorization reachable over the network by an authenticated low-privilege user (PR:L) with no interaction, yielding limited confidentiality and integrity impact and no availability loss.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Missing Authorization vulnerability in bPlugins Before After Image Comparison - Image comparison for WP before-after-image-compare allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Before After Image Comparison - Image comparison for WP: from n/a through 1.1.21.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-95746
GHSA-xpr7-4jqm-h3cm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB