# CVE-2024-1158: Missing authorization in Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)

> Authenticated subscribers can create arbitrary published pages due to missing capability checks in the Post Form WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 13 Mar 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-77cp-583r-8x6c

## What is CVE-2024-1158?

CVE-2024-1158 is a medium-severity missing authorization vulnerability in themekraft Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC), published on 13 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the buddyforms_new_page function in all versions up to, and including, 2.8.7. This makes it possible for authenticated attackers, with subscriber access or higher, to create pages with arbitrary titles. These pages are published.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Themekraft Buddyforms.

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

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

## Is CVE-2024-1158 being exploited?

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

## Other vulnerabilities in themekraft Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)

- [CVE-2023-26326](https://insights.sbomify.com/CVE-2023-26326/): Deserialization in BuddyForms WordPress Plugin (critical 9.8)
- [CVE-2018-21003](https://insights.sbomify.com/CVE-2018-21003/): SQL injection in n/a (critical 9.8)
- [CVE-2024-8246](https://insights.sbomify.com/CVE-2024-8246/): Privilege escalation in Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) (high 8.8)
- [CVE-2024-32830](https://insights.sbomify.com/CVE-2024-32830/): WordPress buddyforms plugin <= 2.8.8- Arbitrary File Read and SSRF vulnerability (high 8.6)
- [CVE-2025-32151](https://insights.sbomify.com/CVE-2025-32151/): WordPress BuddyForms plugin <= 2.10.2 - Local File Inclusion vulnerability (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1158 is a medium-severity missing authorization vulnerability in themekraft Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC), published on 13 Mar 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-1158 in the wild and no public exploit code.

Affected product: themekraft Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC). 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-1158/ (Markdown: https://insights.sbomify.com/CVE-2024-1158/index.md)
```

## Sources

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

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