<?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>Sat, 03 Oct 2026 06:41:15 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-55477</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-55477</link>
      <description>&lt;p&gt;3X-UI is a web control panel for managing Xray-core servers. Prior to 3.3.1, an authenticated administrator can abuse the database import functionality to achieve arbitrary file write on the host by modifying Xray configuration values stored in the database. This can be leveraged to obtain code execution and persistent access as the user running Xray (including root when Xray is running as root). This vulnerability is fixed in 3.3.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;3X-UI is a web control panel for managing Xray-core servers. Prior to 3.3.1, an authenticated administrator can abuse the database import functionality to achieve arbitrary file write on the host by modifying Xray configuration values stored in the database. This can be leveraged to obtain code execution and persistent access as the user running Xray (including root when Xray is running as root). This vulnerability is fixed in 3.3.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-55477</guid>
    </item>
    <item>
      <title>GHSA-jm48-m3rr-9hgg — 3X-UI Vulnerable to Authenticated Arbitrary File Write via Database Import and Xray Log Path Manipulation</title>
      <link>https://db.gcve.eu/vuln/ghsa-jm48-m3rr-9hgg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/mhsanaei/3x-ui/v3, Go: github.com/mhsanaei/3x-ui/v2&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;An authenticated administrator can abuse the database import functionality to achieve arbitrary file write on the host by modifying Xray configuration values stored in the database. This can be leveraged to obtain code execution and persistent access as the user running Xray (including root when Xray is running as root).&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;The database import functionality trusts attacker-controlled configuration values without sufficient validation.&lt;/p&gt;
&lt;p&gt;An authenticated administrator can export the SQLite database, modify `xrayTemplateConfig.log.access` to point to an arbitrary file, and import the modified database back into the panel. The attacker can then inject controlled content into an inbound client&amp;#39;s `email` field. When a connection is processed, Xray writes the attacker-controlled content to the configured access log path.&lt;/p&gt;
&lt;p&gt;Because the log path is fully attacker-controlled, this behavior results in arbitrary file write as the user running Xray. Depending on the target file and service privileges, this can be used to obtain code execution and persistent host access.&lt;/p&gt;
&lt;p&gt;# PoC&lt;/p&gt;
&lt;p&gt;1. Authenticate as a panel administrator.
2. Export the panel database.
3. Modify `xrayTemplateConfig.log.access` to point to a writable target file (e.g. `~/.ssh/authorized_keys`).
4. Inject an attacker-controlled SSH public key into an inbound client&amp;#39;s `email` field.
5. Import the modified database.
6. Trigger a connection through the modified inbound.
7. Xray writes the attacker-controlled co…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/mhsanaei/3x-ui/v3, Go: github.com/mhsanaei/3x-ui/v2&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;An authenticated administrator can abuse the database import functionality to achieve arbitrary file write on the host by modifying Xray configuration values stored in the database. This can be leveraged to obtain code execution and persistent access as the user running Xray (including root when Xray is running as root).&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;The database import functionality trusts attacker-controlled configuration values without sufficient validation.&lt;/p&gt;
&lt;p&gt;An authenticated administrator can export the SQLite database, modify `xrayTemplateConfig.log.access` to point to an arbitrary file, and import the modified database back into the panel. The attacker can then inject controlled content into an inbound client&amp;#39;s `email` field. When a connection is processed, Xray writes the attacker-controlled content to the configured access log path.&lt;/p&gt;
&lt;p&gt;Because the log path is fully attacker-controlled, this behavior results in arbitrary file write as the user running Xray. Depending on the target file and service privileges, this can be used to obtain code execution and persistent host access.&lt;/p&gt;
&lt;p&gt;# PoC&lt;/p&gt;
&lt;p&gt;1. Authenticate as a panel administrator.
2. Export the panel database.
3. Modify `xrayTemplateConfig.log.access` to point to a writable target file (e.g. `~/.ssh/authorized_keys`).
4. Inject an attacker-controlled SSH public key into an inbound client&amp;#39;s `email` field.
5. Import the modified database.
6. Trigger a connection through the modified inbound.
7. Xray writes the attacker-controlled co…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-jm48-m3rr-9hgg</guid>
    </item>
  </channel>
</rss>
