<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-16T21:05:37.717876+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-406633</id>
    <title>EUVD-2026-406633</title>
    <updated>2026-11-16T21:05:37.719531+00:00</updated>
    <content>EUVD-2026-406633</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-406633"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-8269-9p52-9cvv</id>
    <title>GHSA-8269-9p52-9cvv</title>
    <updated>2026-11-16T21:05:37.719565+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The Shipo plugin for WordPress is vulnerable to Authentication Bypass in versions 1.6 through 1.8.0. This is due to the `authenticate_rest_user()` function parsing the `LOGGED_IN_COOKIE` value and authenticating the named user without verifying the cookie's cryptographic signature. The function's intended `/wp-json/shipo/` route restriction can also be bypassed by placing that substring in the query string of an unrelated REST endpoint. This makes it possible for unauthenticated attackers who know an existing username to impersonate that user, including an administrator, and perform authorized actions through the REST API, including creating another administrator account.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-8269-9p52-9cvv"/>
  </entry>
</feed>
