# CVE-2024-12470: School Management System – SakolaWP <= 1.0.8 - Unauthenticated Privilege Escalation

> Unauthenticated attackers can register as administrators due to improper role restriction in the registration function.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9g93-pxpv-276m

## What is CVE-2024-12470?

CVE-2024-12470 is a critical vulnerability in themesawesome School Management System – SakolaWP, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The School Management System – SakolaWP plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.0.8. This is due to the registration function not properly limiting what roles a user can register as. This makes it possible for unauthenticated attackers to register as an administrative user.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2024-12470?


## How do I fix CVE-2024-12470?

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

## Is CVE-2024-12470 being exploited?

There is no known exploitation of CVE-2024-12470 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12470 and fix it if it is affected.

What it is: CVE-2024-12470 is a critical vulnerability in themesawesome School Management System – SakolaWP, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12470 in the wild and no public exploit code.

Affected product: themesawesome School Management System – SakolaWP. 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-2024-12470/ (Markdown: https://insights.sbomify.com/CVE-2024-12470/index.md)
```

## Sources

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

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