<?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>Mon, 28 Sep 2026 17:24:02 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-100720</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-100720</link>
      <description>&lt;p&gt;Froxlor 2.0.0 through 2.3.10 is vulnerable to stored cross-site scripting. When a customer (the lowest-privileged authenticated role) uploads an SSL certificate for one of their own domains, the Certificates API add()/update() methods parse it with openssl_x509_parse() and store the issuer organization (issuer[&amp;#39;O&amp;#39;]) value verbatim without sanitization. Froxlor&amp;#39;s table-listing renderer then emits scalar cells through Twig&amp;#39;s `raw` filter, disabling HTML auto-escaping, so when an administrator or reseller opens Domains &amp;gt; SSL certificates the attacker-supplied issuer value executes as script in the privileged user&amp;#39;s session. This crosses a privilege boundary from customer to admin and can result in full administrator account takeover; because a Froxlor admin controls webserver, DNS, and PHP configuration applied by a cron job running as root, the issue can be further escalated to command execution as root on the managed server. The issue is fixed in Froxlor 2.3.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Froxlor 2.0.0 through 2.3.10 is vulnerable to stored cross-site scripting. When a customer (the lowest-privileged authenticated role) uploads an SSL certificate for one of their own domains, the Certificates API add()/update() methods parse it with openssl_x509_parse() and store the issuer organization (issuer[&amp;#39;O&amp;#39;]) value verbatim without sanitization. Froxlor&amp;#39;s table-listing renderer then emits scalar cells through Twig&amp;#39;s `raw` filter, disabling HTML auto-escaping, so when an administrator or reseller opens Domains &amp;gt; SSL certificates the attacker-supplied issuer value executes as script in the privileged user&amp;#39;s session. This crosses a privilege boundary from customer to admin and can result in full administrator account takeover; because a Froxlor admin controls webserver, DNS, and PHP configuration applied by a cron job running as root, the issue can be further escalated to command execution as root on the managed server. The issue is fixed in Froxlor 2.3.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-100720</guid>
    </item>
    <item>
      <title>GHSA-mmqp-fgp4-5q7j</title>
      <link>https://db.gcve.eu/vuln/ghsa-mmqp-fgp4-5q7j</link>
      <description>&lt;p&gt;Froxlor 2.0.0 through 2.3.10 is vulnerable to stored cross-site scripting. When a customer (the lowest-privileged authenticated role) uploads an SSL certificate for one of their own domains, the Certificates API add()/update() methods parse it with openssl_x509_parse() and store the issuer organization (issuer[&amp;#39;O&amp;#39;]) value verbatim without sanitization. Froxlor&amp;#39;s table-listing renderer then emits scalar cells through Twig&amp;#39;s `raw` filter, disabling HTML auto-escaping, so when an administrator or reseller opens Domains &amp;gt; SSL certificates the attacker-supplied issuer value executes as script in the privileged user&amp;#39;s session. This crosses a privilege boundary from customer to admin and can result in full administrator account takeover; because a Froxlor admin controls webserver, DNS, and PHP configuration applied by a cron job running as root, the issue can be further escalated to command execution as root on the managed server. The issue is fixed in Froxlor 2.3.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Froxlor 2.0.0 through 2.3.10 is vulnerable to stored cross-site scripting. When a customer (the lowest-privileged authenticated role) uploads an SSL certificate for one of their own domains, the Certificates API add()/update() methods parse it with openssl_x509_parse() and store the issuer organization (issuer[&amp;#39;O&amp;#39;]) value verbatim without sanitization. Froxlor&amp;#39;s table-listing renderer then emits scalar cells through Twig&amp;#39;s `raw` filter, disabling HTML auto-escaping, so when an administrator or reseller opens Domains &amp;gt; SSL certificates the attacker-supplied issuer value executes as script in the privileged user&amp;#39;s session. This crosses a privilege boundary from customer to admin and can result in full administrator account takeover; because a Froxlor admin controls webserver, DNS, and PHP configuration applied by a cron job running as root, the issue can be further escalated to command execution as root on the managed server. The issue is fixed in Froxlor 2.3.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-mmqp-fgp4-5q7j</guid>
    </item>
  </channel>
</rss>
