<?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://cve.radiocsirt.org</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>Thu, 15 Oct 2026 14:24:09 +0000</lastBuildDate>
    <item>
      <title>BIT-parse-2020-5251 — Information disclosure in parse-server</title>
      <link>https://cve.radiocsirt.org/vuln/bit-parse-2020-5251</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: parse&lt;/p&gt;
&lt;p&gt;In parser-server before version 4.1.0, you can fetch all the users objects, by using regex in the NoSQL query. Using the NoSQL, you can use a regex on sessionToken and find valid accounts this way.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: parse&lt;/p&gt;
&lt;p&gt;In parser-server before version 4.1.0, you can fetch all the users objects, by using regex in the NoSQL query. Using the NoSQL, you can use a regex on sessionToken and find valid accounts this way.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-parse-2020-5251</guid>
    </item>
    <item>
      <title>EUVD-2026-36474</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-36474</link>
      <description>EUVD-2026-36474</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-36474</guid>
    </item>
    <item>
      <title>fkie_cve-2020-5251</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-5251</link>
      <description>&lt;p&gt;In parser-server before version 4.1.0, you can fetch all the users objects, by using regex in the NoSQL query. Using the NoSQL, you can use a regex on sessionToken and find valid accounts this way.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In parser-server before version 4.1.0, you can fetch all the users objects, by using regex in the NoSQL query. Using the NoSQL, you can use a regex on sessionToken and find valid accounts this way.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-5251</guid>
    </item>
    <item>
      <title>GHSA-h4mf-75hf-67w4 — Information disclosure in parse-server</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h4mf-75hf-67w4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: parse-server&lt;/p&gt;
&lt;p&gt;1. you can fetch all the users&amp;#39; objects, by using regex in the NoSQL query.
Using the NoSQL, you can use a regex on sessionToken `(&amp;#34;_SessionToken&amp;#34;:{&amp;#34;$regex&amp;#34;:&amp;#34;r:027f&amp;#34;}}` and find valid accounts this way.&lt;/p&gt;
&lt;p&gt;Using this method, it&amp;#39;s possible to retrieve accounts without interaction from the users.&lt;/p&gt;
&lt;p&gt;GET /parse/users/me HTTP/1.1
```
{
  &amp;#34;_ApplicationId&amp;#34;: &amp;#34;appName&amp;#34;,
  &amp;#34;_JavaScriptKey&amp;#34;: &amp;#34;javascriptkey&amp;#34;,
  &amp;#34;_ClientVersion&amp;#34;: &amp;#34;js2.10.0&amp;#34;,
  &amp;#34;_InstallationId&amp;#34;: &amp;#34;ca713ee2-6e60-d023-a8fe-14e1bfb2f300&amp;#34;,
  &amp;#34;_SessionToken&amp;#34;: {
    &amp;#34;$regex&amp;#34;: &amp;#34;r:5&amp;#34;
  }
}
```
When trying it with an update query the same thing luckily doesn&amp;#39;t seem to work:
POST /parse/classes/_User/PPNk59jPPZ&lt;/p&gt;
&lt;p&gt;2. There is another similar vulnerability in verify email and the request password reset.&lt;/p&gt;
&lt;p&gt;If you sign up with someone else&amp;#39;s email address, you can simply use regex in the token param to verify the account: `http://localhost:1337/parse/apps/kickbox/verify_email?token[$regex]=a&amp;amp;username=some@email.com`&lt;/p&gt;
&lt;p&gt;The same thing can be done for reset password: `http://localhost:1337/parse/apps/kickbox/request_password_reset?token[$regex]=a&amp;amp;username=some@email.com`&lt;/p&gt;
&lt;p&gt;You may need to do it a few times with a different letter/number, but as long as the tokens contain the character it will succeed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: parse-server&lt;/p&gt;
&lt;p&gt;1. you can fetch all the users&amp;#39; objects, by using regex in the NoSQL query.
Using the NoSQL, you can use a regex on sessionToken `(&amp;#34;_SessionToken&amp;#34;:{&amp;#34;$regex&amp;#34;:&amp;#34;r:027f&amp;#34;}}` and find valid accounts this way.&lt;/p&gt;
&lt;p&gt;Using this method, it&amp;#39;s possible to retrieve accounts without interaction from the users.&lt;/p&gt;
&lt;p&gt;GET /parse/users/me HTTP/1.1
```
{
  &amp;#34;_ApplicationId&amp;#34;: &amp;#34;appName&amp;#34;,
  &amp;#34;_JavaScriptKey&amp;#34;: &amp;#34;javascriptkey&amp;#34;,
  &amp;#34;_ClientVersion&amp;#34;: &amp;#34;js2.10.0&amp;#34;,
  &amp;#34;_InstallationId&amp;#34;: &amp;#34;ca713ee2-6e60-d023-a8fe-14e1bfb2f300&amp;#34;,
  &amp;#34;_SessionToken&amp;#34;: {
    &amp;#34;$regex&amp;#34;: &amp;#34;r:5&amp;#34;
  }
}
```
When trying it with an update query the same thing luckily doesn&amp;#39;t seem to work:
POST /parse/classes/_User/PPNk59jPPZ&lt;/p&gt;
&lt;p&gt;2. There is another similar vulnerability in verify email and the request password reset.&lt;/p&gt;
&lt;p&gt;If you sign up with someone else&amp;#39;s email address, you can simply use regex in the token param to verify the account: `http://localhost:1337/parse/apps/kickbox/verify_email?token[$regex]=a&amp;amp;username=some@email.com`&lt;/p&gt;
&lt;p&gt;The same thing can be done for reset password: `http://localhost:1337/parse/apps/kickbox/request_password_reset?token[$regex]=a&amp;amp;username=some@email.com`&lt;/p&gt;
&lt;p&gt;You may need to do it a few times with a different letter/number, but as long as the tokens contain the character it will succeed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h4mf-75hf-67w4</guid>
    </item>
    <item>
      <title>gsd-2020-5251</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-5251</link>
      <description>gsd-2020-5251</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-5251</guid>
    </item>
  </channel>
</rss>
