<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-25T23:51:29.228035+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-115933</id>
    <title>fkie_cve-2026-115933</title>
    <updated>2026-10-25T23:51:29.245296+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Postiz signs its session, invitation and password reset tokens with one shared secret and without any marker of what a token is for. A route that refreshes the credentials of a browser-extension channel signed data taken from the request itself and stored the result where the requesting user can read it back. A user could therefore obtain a validly signed token containing any claims they choose, which the application accepts as a session, as an organization invitation with a chosen role, as a password reset or as an enterprise provisioning token.</p>
<p>A second, narrower route that creates team invitations signs extra fields from the request body in the same way.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-115933"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-9j6f-8rw3-93c4</id>
    <title>GHSA-9j6f-8rw3-93c4</title>
    <updated>2026-10-25T23:51:29.245358+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Postiz signs its session, invitation and password reset tokens with one shared secret and without any marker of what a token is for. A route that refreshes the credentials of a browser-extension channel signed data taken from the request itself and stored the result where the requesting user can read it back. A user could therefore obtain a validly signed token containing any claims they choose, which the application accepts as a session, as an organization invitation with a chosen role, as a password reset or as an enterprise provisioning token.</p>
<p>A second, narrower route that creates team invitations signs extra fields from the request body in the same way.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-9j6f-8rw3-93c4"/>
  </entry>
</feed>
