Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-110371 Overview
CVE-2026-110371 is a missing authorization vulnerability in the WP Chill Strong Testimonials plugin for WordPress. The flaw affects all versions of strong-testimonials up to and including 3.3.12. It stems from incorrectly configured access control security levels, mapped to [CWE-862]. An authenticated attacker with low privileges can abuse plugin functionality that lacks proper capability checks. The vulnerability requires network access and no user interaction. Impact is limited to confidentiality, with no direct effect on integrity or availability.
Critical Impact
Low-privileged WordPress users can access plugin functionality intended for higher-privileged roles, exposing information managed by the testimonials plugin.
Affected Products
- WP Chill Strong Testimonials plugin for WordPress
- Versions from n/a through 3.3.12
- WordPress sites with the plugin installed and active
Discovery Timeline
- 2026-10-15 - CVE CVE-2026-110371 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-110371
Vulnerability Analysis
The Strong Testimonials plugin exposes functionality without validating the caller's role or capabilities. A broken access control condition allows a user with minimal privileges to invoke actions reserved for site administrators or editors. The issue is limited to confidentiality impact, meaning an attacker can read information rather than modify or destroy it. Exploitation requires an authenticated session on the WordPress instance. Because the attack vector is network based and complexity is low, any valid low-privileged account on an affected site can trigger the flaw.
Root Cause
The plugin fails to perform authorization checks on one or more handlers that should be restricted to privileged roles. Under [CWE-862], the code path executes without verifying that the current user holds the required WordPress capability. This typically occurs when current_user_can() checks are omitted from AJAX actions, REST routes, or admin-post handlers. The access control security level is incorrectly configured, so WordPress treats low-privileged roles as authorized callers.
Attack Vector
An attacker authenticates to the target WordPress site using any account that holds low-level permissions, such as subscriber. The attacker then sends a crafted HTTP request to the plugin endpoint lacking capability enforcement. The server processes the request and returns data that should be gated behind higher privileges. No social engineering or user interaction is required. The vulnerability manifests through standard HTTP traffic to the WordPress admin or REST interface. See the Patchstack Vulnerability Advisory for additional technical context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-110371
Indicators of Compromise
- Unexpected HTTP requests to Strong Testimonials AJAX actions or REST routes originating from low-privileged user sessions.
- Access log entries showing subscriber-level accounts hitting admin-oriented plugin endpoints.
- Repeated requests to admin-ajax.php with Strong Testimonials action parameters outside normal content workflows.
Detection Strategies
- Review WordPress audit logs for authenticated users invoking plugin endpoints inconsistent with their assigned role.
- Correlate web server access logs with user role data to identify authorization anomalies tied to the strong-testimonials plugin.
- Alert on bulk or scripted requests to plugin handlers from accounts that have never interacted with testimonials features.
Monitoring Recommendations
- Enable WordPress activity logging to capture AJAX and REST calls per authenticated user.
- Monitor plugin version inventories to confirm all WordPress sites run a patched release above 3.3.12.
- Track newly created low-privileged accounts followed by requests to plugin endpoints as a potential exploitation pattern.
How to Mitigate CVE-2026-110371
Immediate Actions Required
- Update the Strong Testimonials plugin to a release later than 3.3.12 as soon as the vendor publishes a fixed version.
- Audit WordPress user accounts and remove unused or unknown low-privileged accounts.
- Restrict user registration on sites that do not require it, reducing the pool of accounts able to exploit the flaw.
Patch Information
The vulnerability affects Strong Testimonials versions up to and including 3.3.12. Administrators should consult the Patchstack Vulnerability Advisory for the latest patched version and vendor guidance. Apply updates through the WordPress plugin manager or by replacing the plugin directory with the fixed release.
Workarounds
- Disable the Strong Testimonials plugin until a patched release is installed if the functionality is not critical.
- Apply a web application firewall rule to block unauthenticated or low-privileged access to plugin AJAX and REST endpoints.
- Enforce the principle of least privilege by auditing custom roles that may inherit broader capabilities than intended.
# Configuration example
wp plugin update strong-testimonials
wp plugin deactivate strong-testimonials # temporary workaround
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

