# CVE-2026-124636: kevquirk PureBlog Page Editor content.php save_page path traversal


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-8jcm-2rmf-8v5r

## What is CVE-2026-124636?

CVE-2026-124636 is a medium-severity vulnerability in kevquirk PureBlog, published on 9 Nov 2026. 

### Official description

A security flaw has been discovered in kevquirk PureBlog up to 3.7.2. The affected element is the function save_page of the file includes/lib/content.php of the component Page Editor. Performing a manipulation of the argument page slug results in path traversal. Remote exploitation of the attack is possible. Upgrading to version 3.7.3 is sufficient to fix this issue. The patch is named 71f5b0de2ecb2bb2934048ed40e1155c107484e3. The affected component should be upgraded. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-124636?


## How do I fix CVE-2026-124636?

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

## Is CVE-2026-124636 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124636 and fix it if it is affected.

What it is: CVE-2026-124636 is a medium-severity vulnerability in kevquirk PureBlog, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124636 in the wild and no public exploit code.

Affected product: kevquirk PureBlog. 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-2026-124636/ (Markdown: https://insights.sbomify.com/CVE-2026-124636/index.md)
```

## Sources

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

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