Is CVE-2026-52770 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-52770 being exploited in the wild.

How severe is CVE-2026-52770?

High severity, with a CVSS score of 7.5, published 5 September 2026.

Which products and versions are affected?

yeswiki/yeswiki (Packagist) < 4.6.6, ECOSYSTEM:introduced=0,fixed=4.6.6; YesWiki < 4.6.6.

Is there a fix for CVE-2026-52770?

Yes. yeswiki/yeswiki (Packagist): upgrade to 4.6.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-52770 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-52770?

Check whether you run yeswiki/yeswiki (Packagist) or YesWiki at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-52770: YesWiki SQL injection in Bazar entry-listing APIs

Q: Is there a fix for CVE-2026-52770?

Yes. yeswiki/yeswiki (Packagist): upgrade to 4.6.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-52770 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-52770?

Check whether you run yeswiki/yeswiki (Packagist) or YesWiki at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-52770 · Severity: high · CVSS 7.5 · Published 2026-09-05

YesWiki, a collaborative wiki platform, contains a security flaw in its Bazar entry-listing component. An unauthenticated attacker can exploit this to extract sensitive information from the database, such as user account details and password hashes. This occurs because the system does not properly validate numeric search filters, allowing malicious database commands to be executed.

Technologies: yeswiki/yeswiki (Packagist), YesWiki. Vendors: Packagist, YesWiki.

Quick answers

Is CVE-2026-52770 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-52770 being exploited in the wild.
How severe is CVE-2026-52770?: High severity, with a CVSS score of 7.5, published 5 September 2026.
Which products and versions are affected?: yeswiki/yeswiki (Packagist) < 4.6.6, ECOSYSTEM:introduced=0,fixed=4.6.6; YesWiki < 4.6.6.
Is there a fix for CVE-2026-52770?: Yes. yeswiki/yeswiki (Packagist): upgrade to 4.6.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-52770 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-52770?: Check whether you run yeswiki/yeswiki (Packagist) or YesWiki at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

yeswiki/yeswiki (Packagist): upgrade to 4.6.6 or later
```
composer require yeswiki/yeswiki:^4.6.6
```

Technical details

An unauthenticated SQL injection vulnerability exists in YesWiki's Bazar API due to improper handling of numeric filters in `SearchManager::buildQueriesConditions()`. While the application uses `mysqli_real_escape_string` on input values, it fails to quote these values or perform numeric validation when they are part of a 'number' type field. This allows an attacker to append SQL syntax (e.g., using 'OR') to the numeric expression. By sending crafted GET requests to public routes like `/api/entries/bazarlist`, an attacker can perform boolean-based inference to extract sensitive data from the database. The vulnerability is patched in version 4.6.6.

Affected products

yeswiki yeswiki < 4.6.6

Identifiers

CVE-2026-52770
GHSA-qg78-vmvc-fhjw

Timeline

2026-06-02: disclosed: Initial disclosure on GitHub
2026-07-09: advisory: Advisory published and updated

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.