# CVE-2025-11554: Portabilis i-Educar User Type AccessLevelController.php insecure inherited permissions

> Attackers can exploit insecure inherited permissions in the User Type Handler to bypass authorization controls and escalate privileges.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2025
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-jff6-cpxv-52x3

## What is CVE-2025-11554?

CVE-2025-11554 is a medium-severity missing authorization vulnerability in Portabilis I-Educar, published on 9 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in Portabilis i-Educar up to 2.9.10. Affected by this issue is some unknown functionality of the file app/Http/Controllers/AccessLevelController.php of the component User Type Handler. The manipulation leads to insecure inherited permissions. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 2.12 can resolve this issue. The identifier of the patch is d53365e5656f6499a4deddf89d522814655f769d. It is advisable to upgrade the affected component.

Weakness: CWE-277 (Insecure Inherited Permissions), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-11554?

It affects 1 product.


Products: Portabilis I-Educar.

## How do I fix CVE-2025-11554?

No fix has been published for CVE-2025-11554 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11554 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11554 exists.

Public exploit code:

- Proof of concept for exploitation of the vulnerability described in CVE-2025-11554, which concerns the possibility of a privilege escalation through arbitrary requests to user types change endpoint in the i-Educar software. (github_poc): https://github.com/m3m0o/portabilis-ieducar-user-type-privilege-escalation

## Other vulnerabilities in Portabilis I-Educar

- [CVE-2024-45059](https://insights.sbomify.com/CVE-2024-45059/): Authenticated SQL Injection in i-Educar (high 8.8)
- [CVE-2024-48325](https://insights.sbomify.com/CVE-2024-48325/): SQL injection in n/a (high 8.1)
- [CVE-2024-45058](https://insights.sbomify.com/CVE-2024-45058/): Privilege escalation in i-Educar (high 8.1)
- [CVE-2025-65022](https://insights.sbomify.com/CVE-2025-65022/): i-Educar Authenticated Time-based SQL Injection in `agenda.php` (high 7.2)
- [CVE-2025-65023](https://insights.sbomify.com/CVE-2025-65023/): i-Educar Authenticated Time-based SQL Injection in `funcionario_vinculo_cad.php` (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11554 and fix it if it is affected.

What it is: CVE-2025-11554 is a medium-severity missing authorization vulnerability in Portabilis I-Educar, published on 9 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11554 exists.

Affected product: Portabilis I-Educar. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2025-11554/ (Markdown: https://insights.sbomify.com/CVE-2025-11554/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11554
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11554
- OSV: https://osv.dev/vulnerability/CVE-2025-11554

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11554/
Summaries are generated and may contain mistakes; the official description above is the record.