<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 09 Oct 2026 21:59:02 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-52775</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-52775</link>
      <description>&lt;p&gt;YesWiki is a wiki system written in PHP. Prior to version 4.6.6, YesWiki through the latest development branch contains a SQL injection vulnerability in ReactionManager::deleteUserReaction() that allows any authenticated user to inject arbitrary SQL via the {idreaction} and {id} URL path parameters. The parameters are concatenated directly into a SQL LIKE clause without escaping or parameterization. This issue has been patched in version 4.6.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;YesWiki is a wiki system written in PHP. Prior to version 4.6.6, YesWiki through the latest development branch contains a SQL injection vulnerability in ReactionManager::deleteUserReaction() that allows any authenticated user to inject arbitrary SQL via the {idreaction} and {id} URL path parameters. The parameters are concatenated directly into a SQL LIKE clause without escaping or parameterization. This issue has been patched in version 4.6.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-52775</guid>
    </item>
    <item>
      <title>GHSA-4pf7-cc4r-g63h — YesWiki has Authenticated SQL Injection via ReactionManager</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-4pf7-cc4r-g63h</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: yeswiki/yeswiki&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;YesWiki through the latest development branch contains a SQL injection vulnerability in `ReactionManager::deleteUserReaction()` that allows any authenticated user to inject arbitrary SQL via the `{idreaction}` and `{id}` URL path parameters. The parameters are concatenated directly into a SQL LIKE clause without escaping or parameterization.&lt;/p&gt;
&lt;p&gt;This is a sibling of CVE-2026-46670 (unauthenticated SQLi in `FormManager::create()`). Both share the same root cause — raw string concatenation into SQL queries — but exist in different components.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;`includes/controllers/ApiController.php` line 726:
```php
/**
 * @Route(&amp;#34;/api/reactions/{idreaction}/{id}/{page}/{username}&amp;#34;, methods={&amp;#34;DELETE&amp;#34;}, options={&amp;#34;acl&amp;#34;:{&amp;#34;+&amp;#34;}})
 */
```&lt;/p&gt;
&lt;p&gt;ACL `&amp;#34;+&amp;#34;` = any authenticated user. Parameters flow into `ReactionManager::deleteUserReaction()` → `TripleStore::delete()` with raw string concatenation into SQL LIKE clause (line 356).&lt;/p&gt;
&lt;p&gt;The `if` branch (lines 340-354) properly uses `$this-&amp;gt;dbService-&amp;gt;escape()`. The `else` branch does not — the developer applied escaping to one code path but not the other.&lt;/p&gt;
&lt;p&gt;## PoC&lt;/p&gt;
&lt;p&gt;```
DELETE /wiki/?api/reactions/x%27%20OR%201=1%20OR%20value%20LIKE%20%27/test/SomePage/attacker
Host: localhost:8085
Cookie: &amp;lt;session cookie&amp;gt;
```&lt;/p&gt;
&lt;p&gt;Time-based blind variant via `{id}` parameter for data exfiltration.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Full database read/write. Any self-registered user can extract `yeswiki_users` password hashes and emails.&lt;/p&gt;
&lt;p&gt;## Suggested Fix&lt;/p&gt;
&lt;p&gt;Apply `$this-&amp;gt;dbService-&amp;gt;e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: yeswiki/yeswiki&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;YesWiki through the latest development branch contains a SQL injection vulnerability in `ReactionManager::deleteUserReaction()` that allows any authenticated user to inject arbitrary SQL via the `{idreaction}` and `{id}` URL path parameters. The parameters are concatenated directly into a SQL LIKE clause without escaping or parameterization.&lt;/p&gt;
&lt;p&gt;This is a sibling of CVE-2026-46670 (unauthenticated SQLi in `FormManager::create()`). Both share the same root cause — raw string concatenation into SQL queries — but exist in different components.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;`includes/controllers/ApiController.php` line 726:
```php
/**
 * @Route(&amp;#34;/api/reactions/{idreaction}/{id}/{page}/{username}&amp;#34;, methods={&amp;#34;DELETE&amp;#34;}, options={&amp;#34;acl&amp;#34;:{&amp;#34;+&amp;#34;}})
 */
```&lt;/p&gt;
&lt;p&gt;ACL `&amp;#34;+&amp;#34;` = any authenticated user. Parameters flow into `ReactionManager::deleteUserReaction()` → `TripleStore::delete()` with raw string concatenation into SQL LIKE clause (line 356).&lt;/p&gt;
&lt;p&gt;The `if` branch (lines 340-354) properly uses `$this-&amp;gt;dbService-&amp;gt;escape()`. The `else` branch does not — the developer applied escaping to one code path but not the other.&lt;/p&gt;
&lt;p&gt;## PoC&lt;/p&gt;
&lt;p&gt;```
DELETE /wiki/?api/reactions/x%27%20OR%201=1%20OR%20value%20LIKE%20%27/test/SomePage/attacker
Host: localhost:8085
Cookie: &amp;lt;session cookie&amp;gt;
```&lt;/p&gt;
&lt;p&gt;Time-based blind variant via `{id}` parameter for data exfiltration.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Full database read/write. Any self-registered user can extract `yeswiki_users` password hashes and emails.&lt;/p&gt;
&lt;p&gt;## Suggested Fix&lt;/p&gt;
&lt;p&gt;Apply `$this-&amp;gt;dbService-&amp;gt;e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-4pf7-cc4r-g63h</guid>
    </item>
  </channel>
</rss>
