# GHSA-xfx2-prg5-jq3g: INSATutorat has an authorization bypass vulnerability in its /api/admin/* endpoints

> Standard users can bypass authorization checks to read sensitive data and modify resources via admin API endpoints.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Mar 2026
- **Also known as:** GO-2026-4581

## What is GHSA-xfx2-prg5-jq3g?

GHSA-xfx2-prg5-jq3g is an authentication bypass vulnerability in github.com/romitou/insatutorat, published on 1 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Impact

An authorization bypass vulnerability was discovered in the administration pages of the tutoring application. When a standard user (logged in but without administrator privileges) attempts to access a resource under /api/admin/, the system detects the error but does not block the request.

As a result, sensitive data is still transmitted by the server in the request (GET), and modification actions such as campaign creation (POST) are executed successfully despite the FORBIDDEN error message. All /api/admin/* endpoints are affected.

### Remediation

The issue was resolved by adding the missing c.Abort() instruction in the Gin authentication middleware (commit 15ae474). This instruction immediately interrupts the processing chain if the user is not an administrator.

### Workarounds

There is no workaround other than applying the fix in the source code.

### Resources:
* Link to the fix commit: [15ae474](https://github.com/Romitou/INSATutorat/commit/15ae47425aed337181f7a6c54a9d199c93b041eb)

### Credits
INSATutorat thanks the Master 2 SSI 25-26 team at the University of Rouen Normandie for their research work on this project.
- Malak Bekkai
- Matthieu Espada Mora
- Amen Allah Khalf Allah
- Liam Laouenan
- Neila Ould Slimane
- Lucas Thomire

This advisory was translated from French to English by GitHub Copilot.

## Which versions are affected by GHSA-xfx2-prg5-jq3g?

3 open source packages ship an affected version, including github.com/romitou/insatutorat.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/romitou/insatutorat` | Go | All versions | 0.0.0-20260226075457-15ae47425aed |
| `github.com/romitou/insatutorat` | Go | All versions | 0.0.0-20260226075457-15ae47425aed |
| `github.com/romitou/insatutorat` | Go | All versions | 0.0.0-20260226075457-15ae47425aed |

## How do I fix GHSA-xfx2-prg5-jq3g?

Upgrade github.com/romitou/insatutorat to 0.0.0-20260226075457-15ae47425aed or later.

## Is GHSA-xfx2-prg5-jq3g being exploited?

There is no known exploitation of GHSA-xfx2-prg5-jq3g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-xfx2-prg5-jq3g and fix it if it is affected.

What it is: GHSA-xfx2-prg5-jq3g is an authentication bypass vulnerability in github.com/romitou/insatutorat, published on 1 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-xfx2-prg5-jq3g in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/romitou/insatutorat (Go): affected all versions; fixed in 0.0.0-20260226075457-15ae47425aed
- github.com/romitou/insatutorat (Go): affected all versions; fixed in 0.0.0-20260226075457-15ae47425aed
- github.com/romitou/insatutorat (Go): affected all versions; fixed in 0.0.0-20260226075457-15ae47425aed

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-xfx2-prg5-jq3g/ (Markdown: https://insights.sbomify.com/GHSA-xfx2-prg5-jq3g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-xfx2-prg5-jq3g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-xfx2-prg5-jq3g/
Summaries are generated and may contain mistakes; the official description above is the record.