# CVE-2026-105877: WordPress QA Analytics plugin <= 5.3.0.0 - Sensitive Data Exposure vulnerability

> An attacker can retrieve embedded sensitive data from the QA Analytics plugin, exposing confidential information to unauthorized users.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-h86h-v9f3-5qp7

## What is CVE-2026-105877?

CVE-2026-105877 is a medium-severity vulnerability in QuarkA QA Analytics, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insertion of Sensitive Information Into Sent Data vulnerability in QuarkA QA Analytics qa-heatmap-analytics allows Retrieve Embedded Sensitive Data.This issue affects QA Analytics: from n/a through 5.3.0.0.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2026-105877?


## How do I fix CVE-2026-105877?

No fix has been published for CVE-2026-105877 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105877 being exploited?

There is no known exploitation of CVE-2026-105877 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105877 and fix it if it is affected.

What it is: CVE-2026-105877 is a medium-severity vulnerability in QuarkA QA Analytics, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105877 in the wild and no public exploit code.

Affected product: QuarkA QA Analytics. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105877/ (Markdown: https://insights.sbomify.com/CVE-2026-105877/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105877
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105877
- OSV: https://osv.dev/vulnerability/CVE-2026-105877

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105877/
Summaries are generated and may contain mistakes; the official description above is the record.