YesWiki: SQL Injection possible through public Bazar entry-listing APIs via numeric query/queries filters

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-52770: 0.47% estimated exploitation activity in the next 30 days; percentile 40.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary YesWiki’s public Bazar entry-listing APIs are vulnerable to unauthenticated SQL injection in numeric query / queries filters. For Bazar fields whose value structure is numeric, YesWiki escapes the attacker-controlled filter value but inserts it into SQL without quotes or numeric validation. An unauthenticated attacker can inject boolean SQL expressions and infer database contents from whether entries are returned. Details The public Bazar API reads attacker-controlled query filters from GET parameters: Relevant public routes include: The query is passed into BazarListService::getEntries() and then into SearchManager::search(): The vulnerable sink is in SearchManager::buildQueriesConditions(): Because numeric values are not quoted, SQL syntax remains active after escaping. For example, the following value is accepted as part of the numeric expression: This produces a predicate equivalent to: Read ACL filtering and Bazar Guard processing do not prevent exploitation because the…

Published by the source

9 Jul 2026, 21:00 UTC

Last modified by the source

9 Jul 2026, 21:00 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qg78-vmvc-fhjw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-52770

Advisory: YesWiki: SQL Injection possible through public Bazar entry-listing APIs via numeric `query`/`queries` filters
IDs: CVE-2026-52770, GHSA-qg78-vmvc-fhjw
Record: https://patchnext.com/advisories/cve-2026-52770 (revision 1, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: yeswiki/yeswiki 4.6.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist yeswiki/yeswiki: affected < 4.6.6; fixed in 4.6.6

## Suggested inspection (read-only)
- Packagist yeswiki/yeswiki: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on yeswiki/yeswiki.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qg78-vmvc-fhjw (GitHub-reviewed advisory GHSA-qg78-vmvc-fhjw lists affected ranges: Packagist yeswiki/yeswiki >=0 <4.6.6)

Commands are suggestions: review each one before running it.