GHSA-5q8v-j673-m5v4: Grumpydictator/firefly iii Firefly III User API Endpoints Vulnerability

MODERATE
CWE-863
Published
Advisory Summary

GHSA-5q8v-j673-m5v4 is a MODERATE firefly iii user api endpoints vulnerability (CWE-863: Incorrect Authorization) affecting Grumpydictator/firefly iii libraries in the Packagist ecosystem. The issue involves firefly iii user api endpoints expose all users' information to any authenticated user (idor). Remediation is available by upgrading affected packages to version 6.5.1.

GHSA-5q8v-j673-m5v4 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-5q8v-j673-m5v4
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product Grumpydictator/firefly iii
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-5q8v-j673-m5v4

To remediate this vulnerability, upgrade all affected Grumpydictator/firefly iii dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

grumpydictator/firefly-iii fixed: 6.5.1
Upgrade grumpydictator/firefly-iii to 6.5.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for grumpydictator/firefly-iii

How to Check if You Are Affected

To determine whether your application is affected by GHSA-5q8v-j673-m5v4, inspect your project dependencies for Grumpydictator/firefly iii:

inspect dependencies for grumpydictator/firefly-iii

Analyze the terminal output to locate any version of Grumpydictator/firefly iii in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.5.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Grumpydictator/firefly iii, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The User management API endpoints (`GET /api/v1/users` and `GET /api/v1/users/{id}`) are accessible to any authenticated user without admin/owner role verification, exposing all users' email addresses, roles, and account status. ### Affected Endpoints 1. **GET /api/v1/users** (UserController::index, line 94) — Lists ALL users with full details. No role check. 2. **GET /api/v1/users/{id}** (UserController::show, line 126) — Shows any user's details by ID. No role check. ### Root Cause (1-of-N Inconsistency) Other methods in the same controller properly check for the 'owner' role: - `store()` — `UserStoreRequest::authorize()` checks `auth()->user()->hasRole('owner')` ✓ - `destroy()` — Explicitly checks `$this->repository->hasRole($admin, 'owner')` ✓ But `index()` and `show()` have no role check at all. The route group at `routes/api.php:734-747` has no admin middleware, only the global `auth:api` middleware. ### Exposed Data The `UserTransformer` (line 40-54) returns: - `email` — user's email address - `role` — user's role (owner/demo) - `blocked` — account blocked status - `blocked_code` — block reason - `created_at` / `updated_at` — timestamps ### Impact Any authenticated user can: 1. Enumerate ALL user accounts in the instance 2. Harvest email addresses for phishing/social engineering 3. Identify admin/owner accounts by role 4. Determine which accounts are blocked ### Exploitation ```bash # List all users curl -H "Authorization: Bearer <any_user_token>" https://instance/api/v1/users # View specific user details curl -H "Authorization: Bearer <any_user_token>" https://instance/api/v1/users/1 ``` ### Suggested Fix Add owner role checks to `index()` and `show()`, or restrict the route group with admin middleware: ```php // Option 1: Add check in controller methods public function show(User $user): JsonResponse { if (!$this->repository->hasRole(auth()->user(), 'owner') && auth()->user()->id !== $user->id) { throw new FireflyException('200025: No access to function.'); } // ... } // Option 2: Add middleware to route group Route::group(['middleware' => ['admin'], ...], ...) ```

GHSA-5q8v-j673-m5v4 Affected Grumpydictator/firefly iii Versions

1 component(s)
Fixed Versions:
6.5.1
Product / Package Ecosystem Affected Versions Fixed Version
grumpydictator/firefly-iii
Packagist
≥ 6.4.23
< 6.5.1
6.5.1

References

Frequently Asked Questions

What is GHSA-5q8v-j673-m5v4?
GHSA-5q8v-j673-m5v4 is a security vulnerability in Grumpydictator/firefly iii involving Firefly III user API endpoints expose all users' information to any authenticated user (IDOR) under CWE-863: Incorrect Authorization.
Which Grumpydictator/firefly iii versions are affected?
Affected versions include releases prior to 6.5.1 across affected packages: grumpydictator/firefly-iii.
What version fixes GHSA-5q8v-j673-m5v4?
Upgrading to 6.5.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is grumpydictator/firefly-iii affected?
Yes, grumpydictator/firefly-iii is affected in releases prior to 6.5.1. Upgrade your dependency to 6.5.1 or later.
What CWE is associated with GHSA-5q8v-j673-m5v4?
GHSA-5q8v-j673-m5v4 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Packagist dependencies for GHSA-5q8v-j673-m5v4?
Run the dependency tree command: 'inspect dependencies for grumpydictator/firefly-iii'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5q8v-j673-m5v4",
  "modified" : "2026-03-07T02:10:45Z",
  "published" : "2026-03-07T02:10:45Z",
  "aliases" : [ ],
  "summary" : "Firefly III user API endpoints expose all users' information to any authenticated user (IDOR)",
  "details" : "### Summary\n\nThe User management API endpoints (`GET /api/v1/users` and `GET /api/v1/users/{id}`) are accessible to any authenticated user without admin/owner role verification, exposing all users' email addresses, roles, and account status.\n\n### Affected Endpoints\n\n1. **GET /api/v1/users** (UserController::index, line 94) — Lists ALL users with full details. No role check.\n2. **GET /api/v1/users/{id}** (UserController::show, line 126) — Shows any user's details by ID. No role check.\n\n### Root Cause (1-of-N Inconsistency)\n\nOther methods in the same controller properly check for the 'owner' role:\n\n- `store()` — `UserStoreRequest::authorize()` checks `auth()->user()->hasRole('owner')` ✓\n- `destroy()` — Explicitly checks `$this->repository->hasRole($admin, 'owner')` ✓\n\nBut `index()` and `show()` have no role check at all. The route group at `routes/api.php:734-747` has no admin middleware, only the global `auth:api` middleware.\n\n### Exposed Data\n\nThe `UserTransformer` (line 40-54) returns:\n- `email` — user's email address\n- `role` — user's role (owner/demo)\n- `blocked` — account blocked status\n- `blocked_code` — block reason\n- `created_at` / `updated_at` — timestamps\n\n### Impact\n\nAny authenticated user can:\n1. Enumerate ALL user accounts in the instance\n2. Harvest email addresses for phishing/social engineering\n3. Identify admin/owner accounts by role\n4. Determine which accounts are blocked\n\n### Exploitation\n\n```bash\n# List all users\ncurl -H \"Authorization: Bearer <any_user_token>\" https://instance/api/v1/users\n\n# View specific user details\ncurl -H \"Authorization: Bearer <any_user_token>\" https://instance/api/v1/users/1\n```\n\n### Suggested Fix\n\nAdd owner role checks to `index()` and `show()`, or restrict the route group with admin middleware:\n\n```php\n// Option 1: Add check in controller methods\npublic function show(User $user): JsonResponse\n{\n    if (!$this->repository->hasRole(auth()->user(), 'owner') && auth()->user()->id !== $user->id) {\n        throw new FireflyException('200025: No access to function.');\n    }\n    // ...\n}\n\n// Option 2: Add middleware to route group\nRoute::group(['middleware' => ['admin'], ...], ...)\n```",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "grumpydictator/firefly-iii"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.4.23"
      }, {
        "fixed" : "6.5.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 6.5.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/firefly-iii/firefly-iii/security/advisories/GHSA-5q8v-j673-m5v4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/firefly-iii/firefly-iii"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-07T02:10:45Z",
    "nvd_published_at" : null
  }
}