CVE-2026-52763 is a stored SQL injection vulnerability in YesWiki affecting the recentchanges action. The flaw is caused by insufficient validation and sanitization of the period action argument before it is incorporated into a database query. An attacker able to save wiki content containing a crafted recentchanges invocation can persist malicious input in a page. When that page is later rendered, the application executes the injected SQL in the context of the backend database connection, allowing unauthorized query manipulation and exposure of database contents.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
recentchanges action in untrusted content, and audit existing pages for malicious use of the period argument. Where possible, tighten write access controls from permissive default configurations and ensure the database account used by the application has the minimum privileges necessary to reduce exposure.Patch, then assume compromise.
recentchanges invocations and remove or sanitize any attacker-controlled period arguments that may have been persisted before remediation.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.