# GHSA-r3fg-3r88-6x3f: Ibexa User Settings are accessible on the front-end for anonymous user

> Anonymous users can access their own user settings, such as time zone preferences, on the Ibexa front-end, resulting in limited information disclosure.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2023

## What is GHSA-r3fg-3r88-6x3f?

GHSA-r3fg-3r88-6x3f is a vulnerability in ibexa/user, published on 10 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### 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

## Which versions are affected by GHSA-r3fg-3r88-6x3f?

2 open source packages ship an affected version, including ibexa/user.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ibexa/user` | Packagist | From 4.0.0 | 4.4.3 |
| `ibexa/user` | Packagist | From 4.0.0 | 4.4.3 |

## How do I fix GHSA-r3fg-3r88-6x3f?

Upgrade ibexa/user to 4.4.3 or later.

## Is GHSA-r3fg-3r88-6x3f being exploited?

There is no known exploitation of GHSA-r3fg-3r88-6x3f in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-r3fg-3r88-6x3f and fix it if it is affected.

What it is: GHSA-r3fg-3r88-6x3f is a vulnerability in ibexa/user, published on 10 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-r3fg-3r88-6x3f in the wild and no public exploit code.

Affected packages and fixed versions:
- ibexa/user (Packagist): affected from 4.0.0; fixed in 4.4.3
- ibexa/user (Packagist): affected from 4.0.0; fixed in 4.4.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-r3fg-3r88-6x3f/ (Markdown: https://insights.sbomify.com/GHSA-r3fg-3r88-6x3f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-r3fg-3r88-6x3f

---
From sbomify Insights: https://insights.sbomify.com/GHSA-r3fg-3r88-6x3f/
Summaries are generated and may contain mistakes; the official description above is the record.