rootpwn

medium · CVSS v3 5.4 · EPSS 0.00158

CVE-2026-84095

The wp-review-slider-pro WordPress plugin before version 12.7.12 lacks a capability check on an AJAX handler, allowing any authenticated use

Overview

The wp-review-slider-pro WordPress plugin before version 12.7.12 lacks a capability check on an AJAX handler, allowing any authenticated user to store arbitrary review content. The stored content is later rendered without escaping, enabling stored XSS on public pages. This flaw can be exploited by low‑privileged users to inject malicious scripts into the site.

Description

The wp-review-slider-pro WordPress plugin before 12.7.12 does not perform a capability check on one of its AJAX handlers, and the nonce protecting it is generated for every visitor, allowing any authenticated user, such as a subscriber, to store arbitrary review content which is later output without escaping on public pages, leading to Stored Cross-Site Scripting.

Impact

Confidentiality: attackers can exfiltrate user data or hijack sessions via injected scripts. Integrity: malicious content is stored and displayed as legitimate reviews. Availability: not directly affected. Defenders: site owners, administrators, and subscribers with access to the plugin are at risk.

Remediation

Upgrade wp-review-slider-pro to version 12.7.12 or later. If an upgrade is not possible, disable the vulnerable AJAX endpoint or add a capability check to restrict it to administrators. Ensure all review content is properly escaped (e.g., using wp_kses) before rendering.

Risk context

Severity is medium (CVSS 5.4) with an EPSS of 0.00158, indicating a low probability of exploitation but still relevant for sites using the plugin. Defenders should address promptly to prevent XSS attacks.

Affected products

  • WordPress wp-review-slider-pro

Scores

Severity
medium
CVSS v2
3.5
CVSS v3
5.4
CVSS v4
—
EPSS
0.00158

wordpress plugin stored-xss wp-review-slider-pro medium capability-check ajax nonce

← All CVEs

Related CVEs

medium

CVE-2026-11871

The Team Members WordPress plugin through 9.2 does not perform any authorization or visibility check in an unauthenticated AJAX action that returns full team member records by ID, allowing unauthenticated attackers to enumerate and disclose details, including email addresses and phone numbers, of team members the administrator has not published publicly.

View analysis

medium

CVE-2026-100604

ClawHub (openclaw/clawhub) contains an incorrect authorization vulnerability in the ClawHub application/backend: an organization-owned skill retains the ownerUserId of its original publisher, and transfer and lifecycle authorization checks trust that historical user before requiring current organization privileges. An authenticated user who originally published an organization skill can therefore transfer, delete, or restore that skill — taking control of its trusted name and history — even after their organization privileges have been revoked or downgraded. The issue was confirmed at revision cbfee7343ddc867316dd9b3de6fa8856730f9f41; the complete historical affected range was not established. It is fixed by PR #3680, included in revision 8c2de6c506bb4efabe3f0c2ffb8370b9e23d4650, which was deployed to clawhub.ai on 2026-09-11; self-hosted deployments should update to that revision or a later descendant. The npm CLI and OpenClaw runtime are separate products and are not affected.

View analysis

medium

CVE-2026-100545

OpenClaw (npm package `openclaw`) before 2026.8.1 incorrectly enforces sender tool policies during session-memory filename generation. In affected versions, filename generation created an embedded helper that retained tools which the originating sender's policy had removed. When session-memory filename generation was enabled for an agent reachable by lower-trust senders, model-mediated instructions could cause the helper to invoke tools outside that sender's effective policy; the demonstrated impact was the creation of persistent scheduled work. Exploitability depends on the model acting on the injected instruction and on which tools the helper exposes. The issue is fixed in 2026.8.1; as a workaround, disable session-memory filename generation for agents reachable by lower-trust senders.

View analysis

medium

CVE-2026-100546

OpenClaw (npm package `openclaw`) versions >= 2026.7.2 and < 2026.9.2 contain a race condition in the Discord realtime voice transcript path. Concurrent control-classified voice transcripts could consume speaker context belonging to another participant after an asynchronous control check, causing a transcript to inherit another speaker's owner status. In Discord agent-proxy voice sessions using the affected realtime control path, an utterance from a non-owner participant could reach the downstream agent boundary marked as owner, so owner-sensitive behavior is applied to the wrong speaker. Exploitation depends on concurrent transcript timing and on the tools and commands available to the affected agent. The issue is fixed in 2026.9.2; as a workaround, disable Discord realtime voice for agents that distinguish owner and non-owner senders.

View analysis