<?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>Mon, 12 Oct 2026 06:36:59 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-277431</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-277431</link>
      <description>EUVD-2026-277431</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-277431</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32760</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32760</link>
      <description>&lt;p&gt;File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. In versions 2.61.2 and below, any unauthenticated visitor can register a full administrator account when self-registration (signup = true) is enabled and the default user permissions have perm.admin = true. The signup handler blindly applies all default settings (including Perm.Admin) to the new user without any server-side guard that strips admin from self-registered accounts. The signupHandler is supposed to create unprivileged accounts for new visitors. It contains no explicit user.Perm.Admin = false reset after applying defaults. If an administrator (intentionally or accidentally) configures defaults.perm.admin = true and also enables signup, every account created via the public registration endpoint is an administrator with full control over all files, users, and server settings. This issue has been resolved in version 2.62.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. In versions 2.61.2 and below, any unauthenticated visitor can register a full administrator account when self-registration (signup = true) is enabled and the default user permissions have perm.admin = true. The signup handler blindly applies all default settings (including Perm.Admin) to the new user without any server-side guard that strips admin from self-registered accounts. The signupHandler is supposed to create unprivileged accounts for new visitors. It contains no explicit user.Perm.Admin = false reset after applying defaults. If an administrator (intentionally or accidentally) configures defaults.perm.admin = true and also enables signup, every account created via the public registration endpoint is an administrator with full control over all files, users, and server settings. This issue has been resolved in version 2.62.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32760</guid>
    </item>
    <item>
      <title>GHSA-5gg9-5g7w-hm73 — File Browser Signup Grants Admin When Default Permissions Include Admin</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5gg9-5g7w-hm73</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/filebrowser/filebrowser/v2&lt;/p&gt;
&lt;p&gt;## Summary
Any unauthenticated visitor can register a full administrator account when self-registration ( signup = true ) is enabled and the default user permissions have perm.admin = true. The signup handler blindly applies all default settings - including Perm.Admin - to the
new user without any server-side guard that strips admin from self-registered accounts.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;**Affected file:** http/auth.go&lt;/p&gt;
&lt;p&gt;**Vulnerable code:**
```go
user := &amp;amp;users.User{
    Username: info.Username,
}
d.settings.Defaults.Apply(user)
```&lt;/p&gt;
&lt;p&gt;**`settings.UserDefaults.Apply` (settings/defaults.go):**
```go
func (d *UserDefaults) Apply(u *users.User) {
    u.Perm = d.Perm
    ...
}
```&lt;/p&gt;
&lt;p&gt;**Settings API permits Admin in defaults (http/settings.go):**
```go
var settingsPutHandler = withAdmin(func(_ http.ResponseWriter, r *http.Request, d *data) (int, error) {
    ...
    d.settings.Defaults = req.Defaults
    ...
})
```&lt;/p&gt;
&lt;p&gt;The signupHandler is supposed to create unprivileged accounts for new visitors. It contains no explicit user.Perm.Admin = false reset after Defaults.Apply. If an administrator (intentionally or accidentally) configures defaults.perm.admin = true and also enables signup, every account created via the public registration endpoint is an administrator with full control over all files, users, and server settings.&lt;/p&gt;
&lt;p&gt;## Demo Server Setup&lt;/p&gt;
&lt;p&gt;```bash
docker run -d --name fb-test \
  -p 8080:80 \
  -v /tmp/fb-data:/srv \
  filebrowser/filebrowser:v2.31.2&lt;/p&gt;
&lt;p&gt;ADMIN_TOKEN=$(curl -s -X POST http://loca…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/filebrowser/filebrowser/v2&lt;/p&gt;
&lt;p&gt;## Summary
Any unauthenticated visitor can register a full administrator account when self-registration ( signup = true ) is enabled and the default user permissions have perm.admin = true. The signup handler blindly applies all default settings - including Perm.Admin - to the
new user without any server-side guard that strips admin from self-registered accounts.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;**Affected file:** http/auth.go&lt;/p&gt;
&lt;p&gt;**Vulnerable code:**
```go
user := &amp;amp;users.User{
    Username: info.Username,
}
d.settings.Defaults.Apply(user)
```&lt;/p&gt;
&lt;p&gt;**`settings.UserDefaults.Apply` (settings/defaults.go):**
```go
func (d *UserDefaults) Apply(u *users.User) {
    u.Perm = d.Perm
    ...
}
```&lt;/p&gt;
&lt;p&gt;**Settings API permits Admin in defaults (http/settings.go):**
```go
var settingsPutHandler = withAdmin(func(_ http.ResponseWriter, r *http.Request, d *data) (int, error) {
    ...
    d.settings.Defaults = req.Defaults
    ...
})
```&lt;/p&gt;
&lt;p&gt;The signupHandler is supposed to create unprivileged accounts for new visitors. It contains no explicit user.Perm.Admin = false reset after Defaults.Apply. If an administrator (intentionally or accidentally) configures defaults.perm.admin = true and also enables signup, every account created via the public registration endpoint is an administrator with full control over all files, users, and server settings.&lt;/p&gt;
&lt;p&gt;## Demo Server Setup&lt;/p&gt;
&lt;p&gt;```bash
docker run -d --name fb-test \
  -p 8080:80 \
  -v /tmp/fb-data:/srv \
  filebrowser/filebrowser:v2.31.2&lt;/p&gt;
&lt;p&gt;ADMIN_TOKEN=$(curl -s -X POST http://loca…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5gg9-5g7w-hm73</guid>
    </item>
  </channel>
</rss>
