ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-10142

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

Published Sep 10, 2025 · catalog updated Apr 8, 2026 · PagBank / PagSeguro Connect para WooCommerce

Last checked Nov 4, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-10142. EPSS is 0.41%. Act only if a listed version of PagBank / PagSeguro Connect para WooCommerce is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.41%
Remediation
Vendor / distro source
Affected products
vendor martins56 PagBank / PagSeguro Connect para WooCommerce 0 ≤4.44.3

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor martins56 PagBank / PagSeguro Connect para WooCommerce 0 ≤4.44.30 ≤4.44.3

How to fix CVE-2025-10142

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-10142. EPSS is 0.41%. Act only if a listed version of PagBank / PagSeguro Connect para WooCommerce is installed.

Which versions are affected?

Compare what you have installed with martins56 PagBank / PagSeguro Connect para WooCommerce 0 ≤4.44.3 0 ≤4.44.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.41%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

WordPress security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 10, 2025 · EUVD

    Detected

    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 a

  2. Apr 8, 2026 · EUVD

    Updated

    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 a

Sources

  • CVE.orgVulnerability recordCVE-2025-10142

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-10142

    30-day exploitation probability 0.41%

    first.org
  • EUVDVulnerability recordEUVD-2025-27519

    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 exist

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 23, 2026
  • CVE.orgOct 22, 2026
  • EUVDOct 21, 2026