CVE-2026-105877

QA Assistants – Driven by data <= 5.3.0.0 - Authenticated (Subscriber+) Information Exposure

2026-10-07 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 5.3.0.1
Affected Version
<= 5.3.0.0
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-105877
View all QA Assistants – Driven by data vulnerabilities

At a glance

CVE-2026-105877 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the QA Assistants WordPress plugin, affecting versions <= 5.3.0.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.3.0.1; sites on affected versions should update now. Disclosed October 2026, reported by Ananda Dhakal.

Vulnerability Overview

The QA Assistants – Driven by data plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.3.0.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract sensitive user or configuration data.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in QA Assistants <= 5.3.0.0 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For QA Assistants the fix is 5.3.0.1: builds <= 5.3.0.0 are affected, anything from 5.3.0.1 onward is not.

Remediation

Update to version 5.3.0.1, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: QA Assistants 5.3.0.1 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C