<?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>Thu, 08 Oct 2026 02:00:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-365193</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-365193</link>
      <description>EUVD-2026-365193</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-365193</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53932</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53932</link>
      <description>&lt;p&gt;laravel-backup-restore restores database backups made with spatie/laravel-backup. Prior to version 1.9.4, a crafted backup archive can trigger OS command injection during database restore. This issue has been patched in version 1.9.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;laravel-backup-restore restores database backups made with spatie/laravel-backup. Prior to version 1.9.4, a crafted backup archive can trigger OS command injection during database restore. This issue has been patched in version 1.9.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53932</guid>
    </item>
    <item>
      <title>GHSA-w9mx-xmg4-gc4r — laravel-backup-restore has an OS Command Injection during database restore</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w9mx-xmg4-gc4r</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: wnx/laravel-backup-restore&lt;/p&gt;
&lt;p&gt;## Summary
A crafted backup archive can trigger OS command injection during database restore. The restore workflow extracts a ZIP archive, enumerates files under `db-dumps`, converts the dump path to an absolute path, and passes that path into database import commands that are built as shell command strings.&lt;/p&gt;
&lt;p&gt;The dump filename is not shell-escaped before it is interpolated into commands such as:&lt;/p&gt;
&lt;p&gt;- `mysql ... &amp;lt; {dumpFile}`
- `gunzip -c {dumpFile}` / `gunzip &amp;lt; {dumpFile}`
- `psql ... &amp;lt; {dumpFile}`
- `sqlite3 ... &amp;lt; {dumpFile}`&lt;/p&gt;
&lt;p&gt;Because `Illuminate\Support\Facades\Process::run(string)` uses Symfony `Process::fromShellCommandline()`, shell metacharacters in the dump filename are interpreted by `/bin/sh` on Unix-like systems or by the platform shell on Windows.&lt;/p&gt;
&lt;p&gt;### Impact
If an attacker can cause an operator or automation to restore a malicious backup archive, the attacker can execute arbitrary shell commands as the PHP/Laravel application user on the system performing the restore. This can lead to application compromise, database credential disclosure, tampering with restored data, and further lateral movement depending on deployment permissions.&lt;/p&gt;
&lt;p&gt;This is not about malicious SQL inside the dump. The command injection is carried in the ZIP entry filename under `db-dumps`, before the dump content is imported.&lt;/p&gt;
&lt;p&gt;### Patches
The vulnerability has been fixed in v1.9.4 of the package.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no configuration option that disables the vulnerable code path. Upgrading t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: wnx/laravel-backup-restore&lt;/p&gt;
&lt;p&gt;## Summary
A crafted backup archive can trigger OS command injection during database restore. The restore workflow extracts a ZIP archive, enumerates files under `db-dumps`, converts the dump path to an absolute path, and passes that path into database import commands that are built as shell command strings.&lt;/p&gt;
&lt;p&gt;The dump filename is not shell-escaped before it is interpolated into commands such as:&lt;/p&gt;
&lt;p&gt;- `mysql ... &amp;lt; {dumpFile}`
- `gunzip -c {dumpFile}` / `gunzip &amp;lt; {dumpFile}`
- `psql ... &amp;lt; {dumpFile}`
- `sqlite3 ... &amp;lt; {dumpFile}`&lt;/p&gt;
&lt;p&gt;Because `Illuminate\Support\Facades\Process::run(string)` uses Symfony `Process::fromShellCommandline()`, shell metacharacters in the dump filename are interpreted by `/bin/sh` on Unix-like systems or by the platform shell on Windows.&lt;/p&gt;
&lt;p&gt;### Impact
If an attacker can cause an operator or automation to restore a malicious backup archive, the attacker can execute arbitrary shell commands as the PHP/Laravel application user on the system performing the restore. This can lead to application compromise, database credential disclosure, tampering with restored data, and further lateral movement depending on deployment permissions.&lt;/p&gt;
&lt;p&gt;This is not about malicious SQL inside the dump. The command injection is carried in the ZIP entry filename under `db-dumps`, before the dump content is imported.&lt;/p&gt;
&lt;p&gt;### Patches
The vulnerability has been fixed in v1.9.4 of the package.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no configuration option that disables the vulnerable code path. Upgrading t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w9mx-xmg4-gc4r</guid>
    </item>
  </channel>
</rss>
