<?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>Fri, 02 Oct 2026 10:01:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-338587</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338587</link>
      <description>EUVD-2026-338587</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338587</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45703</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45703</link>
      <description>&lt;p&gt;Pimcore is an Open Source Data &amp;amp; Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.7, the WordExport export flow in bundles/WordExportBundle/src/Controller/TranslationController.php only checks the word_export feature permission and directly resolves attacker-controlled type/id input without enforcing view permission on page, snippet, email, or object elements, allowing a low-privileged backend user to export document content the user is not allowed to view. This issue is fixed in versions 11.5.17 (LTS) and 12.3.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Pimcore is an Open Source Data &amp;amp; Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.7, the WordExport export flow in bundles/WordExportBundle/src/Controller/TranslationController.php only checks the word_export feature permission and directly resolves attacker-controlled type/id input without enforcing view permission on page, snippet, email, or object elements, allowing a low-privileged backend user to export document content the user is not allowed to view. This issue is fixed in versions 11.5.17 (LTS) and 12.3.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-45703</guid>
    </item>
    <item>
      <title>GHSA-332x-r494-54fq — Pimcore has a WordExport Authorization Bypass for Unauthorized Document Export</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-332x-r494-54fq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pimcore/pimcore&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `WordExport` export flow only checks whether the current backend user has the feature permission `word_export`. It does not verify access rights on the target element itself.  
As a result, a low-privileged backend user can export document content even when the user does not have `view` permission on that document.&lt;/p&gt;
&lt;p&gt;In the local Docker reproduction, a low-privileged user successfully exported sensitive content from a page the user was not allowed to view:&lt;/p&gt;
&lt;p&gt;- `POC-WORDEXPORT-TITLE`
- `POC-WORDEXPORT-DESC`&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;The controller only performs a feature-level permission check before starting the export flow:&lt;/p&gt;
&lt;p&gt;- [[TranslationController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L41)](pimcore-12.3.3/bundles/WordExportBundle/src/Controller/[TranslationController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L44)#L41)
- [TranslationController.php](pimcore-12.3.3/bundles/WordExportBundle/src/Controller/[TranslationController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L56)#L44)&lt;/p&gt;
&lt;p&gt;It then directly resolves the target element from attacker-controlled `type/id` input:&lt;/p&gt;
&lt;p&gt;- [[TranslationController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pimcore/pimcore&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `WordExport` export flow only checks whether the current backend user has the feature permission `word_export`. It does not verify access rights on the target element itself.  
As a result, a low-privileged backend user can export document content even when the user does not have `view` permission on that document.&lt;/p&gt;
&lt;p&gt;In the local Docker reproduction, a low-privileged user successfully exported sensitive content from a page the user was not allowed to view:&lt;/p&gt;
&lt;p&gt;- `POC-WORDEXPORT-TITLE`
- `POC-WORDEXPORT-DESC`&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;The controller only performs a feature-level permission check before starting the export flow:&lt;/p&gt;
&lt;p&gt;- [[TranslationController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L41)](pimcore-12.3.3/bundles/WordExportBundle/src/Controller/[TranslationController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L44)#L41)
- [TranslationController.php](pimcore-12.3.3/bundles/WordExportBundle/src/Controller/[TranslationController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/WordExportBundle/src/Controller/TranslationController.php#L56)#L44)&lt;/p&gt;
&lt;p&gt;It then directly resolves the target element from attacker-controlled `type/id` input:&lt;/p&gt;
&lt;p&gt;- [[TranslationController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-332x-r494-54fq</guid>
    </item>
  </channel>
</rss>
