<?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://db.gcve.eu</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>Wed, 11 Nov 2026 23:02:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-120575 — Photo Engine (Media Organizer &amp; Lightroom) &lt;= 6.5.7 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Colle…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-120575</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tigroumeow Photo Engine (Media Organizer &amp;amp; Lightroom)&lt;/p&gt;
&lt;p&gt;The Photo Engine (Media Organizer &amp;amp; Lightroom) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;hierarchy[].name&amp;#39; parameter in all versions up to, and including, 6.5.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by Subscribers because the /?wplr-sync-api endpoint authenticates solely via wplr_auth_token usermeta with no capability check, and the current user&amp;#39;s token is exposed on every admin page via localized script data due to a commented-out screen-condition guard.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tigroumeow Photo Engine (Media Organizer &amp;amp; Lightroom)&lt;/p&gt;
&lt;p&gt;The Photo Engine (Media Organizer &amp;amp; Lightroom) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;hierarchy[].name&amp;#39; parameter in all versions up to, and including, 6.5.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by Subscribers because the /?wplr-sync-api endpoint authenticates solely via wplr_auth_token usermeta with no capability check, and the current user&amp;#39;s token is exposed on every admin page via localized script data due to a commented-out screen-condition guard.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-120575</guid>
    </item>
  </channel>
</rss>
