# CVE-2025-10142: PagBank / PagSeguro Connect para WooCommerce <= 4.44.3 - Authenticated (Shop Manager+) SQL Injection

> Authenticated Shop Managers can exploit SQL injection in the PagBank WooCommerce plugin to extract sensitive database information.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-26rv-qwc7-28pf

## What is CVE-2025-10142?

CVE-2025-10142 is a medium-severity SQL injection vulnerability in martins56 PagBank / PagSeguro Connect para WooCommerce, published on 10 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The PagBank / PagSeguro Connect para WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'status' parameter in all versions up to, and including, 4.44.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for authenticated attackers, with Shop Manager-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-10142?


## How do I fix CVE-2025-10142?

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

## Is CVE-2025-10142 being exploited?

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

Public exploit code:

- Disclosure for CVE-2025-10142 (github_poc): https://github.com/MooseLoveti/PagSeguro-Connect-Para-WooCommerce-CVE-Report

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10142 and fix it if it is affected.

What it is: CVE-2025-10142 is a medium-severity SQL injection vulnerability in martins56 PagBank / PagSeguro Connect para WooCommerce, published on 10 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10142 in the wild and no public exploit code.

Affected product: martins56 PagBank / PagSeguro Connect para WooCommerce. 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-2025-10142/ (Markdown: https://insights.sbomify.com/CVE-2025-10142/index.md)
```

## Sources

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

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