<?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>Tue, 06 Oct 2026 15:12:15 +0000</lastBuildDate>
    <item>
      <title>BIT-ghost-2026-53949 — Ghost Content API filter bypass reveals private fields</title>
      <link>https://cve.radiocsirt.org/vuln/bit-ghost-2026-53949</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: ghost&lt;/p&gt;
&lt;p&gt;Ghost is a Node.js content management system. From 5.46.1 until 6.21.2, the validation applied to filters on the public API endpoints could be partially bypassed, making it possible to reveal private fields via a brute force attack. If SQLite was used as the database password hashes were fully accessible. If MySQL was used as the database the password hashes&amp;#39; case (uppercase / lowercase) would have been lost, which would likely have rendered a further brute force attack on the discovered hashes fruitless. This vulnerability is fixed in 6.21.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: ghost&lt;/p&gt;
&lt;p&gt;Ghost is a Node.js content management system. From 5.46.1 until 6.21.2, the validation applied to filters on the public API endpoints could be partially bypassed, making it possible to reveal private fields via a brute force attack. If SQLite was used as the database password hashes were fully accessible. If MySQL was used as the database the password hashes&amp;#39; case (uppercase / lowercase) would have been lost, which would likely have rendered a further brute force attack on the discovered hashes fruitless. This vulnerability is fixed in 6.21.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-ghost-2026-53949</guid>
    </item>
    <item>
      <title>EUVD-2026-330026</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-330026</link>
      <description>EUVD-2026-330026</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-330026</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53949</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53949</link>
      <description>&lt;p&gt;Ghost is a Node.js content management system. From 5.46.1 until 6.21.2, the validation applied to filters on the public API endpoints could be partially bypassed, making it possible to reveal private fields via a brute force attack. If SQLite was used as the database password hashes were fully accessible. If MySQL was used as the database the password hashes&amp;#39; case (uppercase / lowercase) would have been lost, which would likely have rendered a further brute force attack on the discovered hashes fruitless. This vulnerability is fixed in 6.21.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ghost is a Node.js content management system. From 5.46.1 until 6.21.2, the validation applied to filters on the public API endpoints could be partially bypassed, making it possible to reveal private fields via a brute force attack. If SQLite was used as the database password hashes were fully accessible. If MySQL was used as the database the password hashes&amp;#39; case (uppercase / lowercase) would have been lost, which would likely have rendered a further brute force attack on the discovered hashes fruitless. This vulnerability is fixed in 6.21.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53949</guid>
    </item>
    <item>
      <title>GHSA-jx35-x7fj-vgpr — Ghost Content API filter bypass reveals private fields</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jx35-x7fj-vgpr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: ghost&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The validation applied to filters on the public API endpoints could be partially bypassed, making it possible to reveal private fields via a brute force attack. If SQLite was used as the database password hashes were fully accessible. If MySQL was used as the database the password hashes&amp;#39; case (uppercase / lowercase) would have been lost, which would likely have rendered a further brute force attack on the discovered hashes fruitless.&lt;/p&gt;
&lt;p&gt;### Vulnerable versions&lt;/p&gt;
&lt;p&gt;This vulnerability is present in Ghost from v5.46.1 up to v6.21.1.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;v6.21.2 contains a fix for this issue.&lt;/p&gt;
&lt;p&gt;### How to update&lt;/p&gt;
&lt;p&gt;For self-hosters using Docker, find [Docker&amp;#39;s official Ghost image here](https://hub.docker.com/_/ghost). Updating a Docker-based Ghost instance [is documented here](https://docs.ghost.org/install/docker#updating-ghost).&lt;/p&gt;
&lt;p&gt;If your Ghost is a Ghost-CLI install see our documentation on [updating it to the latest version here](https://docs.ghost.org/update).&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If upgrading immediately is not possible, block or filter requests to Content API endpoints where the `filter` query parameter contains `password` or `email` (including any compound form such as `users.password`, `users.email`, `authors.password`, `authors.email`). Reject requests at a reverse proxy / WAF layer before they reach Ghost.&lt;/p&gt;
&lt;p&gt;Example (case-insensitive) pattern to block on the raw querystring:&lt;/p&gt;
&lt;p&gt;```
filter=[^&amp;amp;]*(password|email)
```&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;Ghost thanks crnkovic for disclosing this v…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: ghost&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The validation applied to filters on the public API endpoints could be partially bypassed, making it possible to reveal private fields via a brute force attack. If SQLite was used as the database password hashes were fully accessible. If MySQL was used as the database the password hashes&amp;#39; case (uppercase / lowercase) would have been lost, which would likely have rendered a further brute force attack on the discovered hashes fruitless.&lt;/p&gt;
&lt;p&gt;### Vulnerable versions&lt;/p&gt;
&lt;p&gt;This vulnerability is present in Ghost from v5.46.1 up to v6.21.1.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;v6.21.2 contains a fix for this issue.&lt;/p&gt;
&lt;p&gt;### How to update&lt;/p&gt;
&lt;p&gt;For self-hosters using Docker, find [Docker&amp;#39;s official Ghost image here](https://hub.docker.com/_/ghost). Updating a Docker-based Ghost instance [is documented here](https://docs.ghost.org/install/docker#updating-ghost).&lt;/p&gt;
&lt;p&gt;If your Ghost is a Ghost-CLI install see our documentation on [updating it to the latest version here](https://docs.ghost.org/update).&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If upgrading immediately is not possible, block or filter requests to Content API endpoints where the `filter` query parameter contains `password` or `email` (including any compound form such as `users.password`, `users.email`, `authors.password`, `authors.email`). Reject requests at a reverse proxy / WAF layer before they reach Ghost.&lt;/p&gt;
&lt;p&gt;Example (case-insensitive) pattern to block on the raw querystring:&lt;/p&gt;
&lt;p&gt;```
filter=[^&amp;amp;]*(password|email)
```&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;Ghost thanks crnkovic for disclosing this v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jx35-x7fj-vgpr</guid>
    </item>
  </channel>
</rss>
