<?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>Thu, 05 Nov 2026 21:46:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-120534 — Advanced Custom Fields: Extended PRO &lt;= 0.9.2.6 - Unauthenticated Remote Code Execution via Dynamic Render Field Type</title>
      <link>https://db.gcve.eu/vuln/cve-2026-120534</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ACF Extended Advanced Custom Fields: Extended PRO&lt;/p&gt;
&lt;p&gt;The Advanced Custom Fields: Extended PRO plugin for WordPress is vulnerable to Limited Code Injection in all versions up to, and including, 0.9.2.6 via the render_field function. This is due to insufficient validation of form configuration parameters before merging into field settings and passing to call_user_func_array in the render_field method. This makes it possible for unauthenticated attackers to call arbitrary WordPress functions with controlled arguments. Method 1 requires the administrator to enable the non-default &amp;#39;shortcode_preview&amp;#39; setting for the target form, while Method 2 requires the server environment to lack OpenSSL functions, causing ACF Pro&amp;#39;s acf_decrypt to fall back to unverified base64 decoding.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ACF Extended Advanced Custom Fields: Extended PRO&lt;/p&gt;
&lt;p&gt;The Advanced Custom Fields: Extended PRO plugin for WordPress is vulnerable to Limited Code Injection in all versions up to, and including, 0.9.2.6 via the render_field function. This is due to insufficient validation of form configuration parameters before merging into field settings and passing to call_user_func_array in the render_field method. This makes it possible for unauthenticated attackers to call arbitrary WordPress functions with controlled arguments. Method 1 requires the administrator to enable the non-default &amp;#39;shortcode_preview&amp;#39; setting for the target form, while Method 2 requires the server environment to lack OpenSSL functions, causing ACF Pro&amp;#39;s acf_decrypt to fall back to unverified base64 decoding.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-120534</guid>
    </item>
  </channel>
</rss>
