# CVE-2025-58827: WordPress Job Board Manager Plugin <= 2.1.61 - Content Injection Vulnerability

> Attackers can inject malicious code into the Job Board Manager plugin, potentially leading to remote code execution on the WordPress site.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-rwmq-jm93-pmpf

## What is CVE-2025-58827?

CVE-2025-58827 is a low-severity code injection vulnerability in PickPlugins Job Board Manager, published on 5 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Control of Generation of Code ('Code Injection') vulnerability in PickPlugins Job Board Manager job-board-manager allows Code Injection.This issue affects Job Board Manager: from n/a through <= 2.1.61.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-58827 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58827 is a low-severity code injection vulnerability in PickPlugins Job Board Manager, published on 5 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58827 in the wild and no public exploit code.

Affected product: PickPlugins Job Board Manager. 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-58827/ (Markdown: https://insights.sbomify.com/CVE-2025-58827/index.md)
```

## Sources

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

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