# CVE-2024-3828: Spectra Pro <= 1.1.5 - Authenticated (Author+) Privilege Escalation

> Authenticated authors can escalate privileges to administrator by setting default registration roles, requiring plugin updates.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 10 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8cpp-w4p7-vjq4

## What is CVE-2024-3828?

CVE-2024-3828 is a high-severity vulnerability in Brainstorm Force Spectra Pro, published on 10 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Spectra Pro plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.1.5. This is due to the plugin allowing lower-privileged users to create registration forms and set the default role to administrator This makes it possible for authenticated attackers, with author-level access and above, to create administrator-level accounts.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-3828 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3828 is a high-severity vulnerability in Brainstorm Force Spectra Pro, published on 10 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3828 in the wild and no public exploit code.

Affected product: Brainstorm Force Spectra Pro. 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-3828/ (Markdown: https://insights.sbomify.com/CVE-2024-3828/index.md)
```

## Sources

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

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