Is CVE-2026-52763 exploited in the wild?

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

How severe is CVE-2026-52763?

Medium severity, with a CVSS score of 6.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-52763?

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-52763 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-52763?

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-52763: YesWiki SQL injection in recentchanges action period argument

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

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-52763 attacked?

It is attacked over the network, in a network appliance.

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

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-52763 · Severity: medium · CVSS 6.5 · Published 2026-09-05

YesWiki, a collaborative wiki platform, contains a security flaw that allows unauthorized access to its internal database. By saving a specially crafted page, an attacker can trick the system into revealing sensitive information, such as user credentials or private site data. This could lead to a full breach of the site's data and compromise of administrative accounts.

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

Quick answers

Is CVE-2026-52763 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-52763 being exploited in the wild.
How severe is CVE-2026-52763?: Medium severity, with a CVSS score of 6.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-52763?: 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-52763 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-52763?: 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

A SQL injection vulnerability exists in YesWiki's `recentchanges` action (`actions/recentchanges.php`). The application fails to validate the `period` argument when it is provided via an action invocation (e.g., `{{recentchanges period="..."}}`), bypassing a whitelist that only applies to URL query parameters. This unvalidated input is passed to `PageManager::getRecentlyChanged()`, where it is directly interpolated into a SQL query without escaping or parameterization. An attacker with page-editing privileges (which are granted to anonymous users by default) can perform UNION-based injection to exfiltrate arbitrary data from the database. The vulnerability is fixed in version 4.6.6.

Affected products

YesWiki yeswiki < 4.6.6

Identifiers

CVE-2026-52763
GHSA-89v6-j5x6-cmj3

Timeline

2026-06-02: disclosed
2026-06-02: patched: Fixed in version 4.6.6
2026-07-09: advisory

References

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