Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4

Ibexa User Settings are accessible on the front-end for anonymous user

GHSA-r3fg-3r88-6x3f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (ibexa/user 4.4.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist ibexa/user

    Affected
    >= 4.0.0, < 4.4.3
    Fixed in
    4.4.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact This security advisory is about the user settings, which include things like preferred time zone and number of items per page in item listings. These could be accessed by the anonymous user. This impacted only the anonymous users themselves, and had no impact on logged in users. As such the impact is limited, even if custom user settings have been added, but please consider if this matters for your site. The fix ensures that only logged in users can access their user settings. References https://developers.ibexa.co/security-advisories/ibexa-sa-2023-002-user-settings-are-accessible-on-the-front-end-for-the-anonymous-user

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-r3fg-3r88-6x3f

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-r3fg-3r88-6x3f

Advisory: Ibexa User Settings are accessible on the front-end for anonymous user
IDs: GHSA-r3fg-3r88-6x3f
Record: https://patchnext.com/advisories/ghsa-r3fg-3r88-6x3f (revision 1, source checked 26 Oct 2026, 14:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ibexa/user 4.4.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ibexa/user: affected >= 4.0.0, < 4.4.3; fixed in 4.4.3

## Suggested inspection (read-only)
- Packagist ibexa/user: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ibexa/user.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r3fg-3r88-6x3f (GitHub-reviewed advisory GHSA-r3fg-3r88-6x3f lists affected ranges: Packagist ibexa/user >=4.0.0 <4.4.3)

Commands are suggestions: review each one before running it.

Loading voting…