# CVE-2025-52713: Server-side request forgery in Post and Page Builder by BoldGrid

> An attacker can exploit a Server-Side Request Forgery vulnerability in the BoldGrid Post and Page Builder plugin to make the server send requests to unintended locations.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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:** 20 Jun 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-5h46-w4wj-65hm

## What is CVE-2025-52713?

CVE-2025-52713 is a medium-severity server-side request forgery vulnerability in Post and Page Builder by BoldGrid, published on 20 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability in BoldGrid Post and Page Builder by BoldGrid post-and-page-builder allows Server Side Request Forgery.This issue affects Post and Page Builder by BoldGrid: from n/a through <= 1.27.8.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2025-52713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52713 is a medium-severity server-side request forgery vulnerability in Post and Page Builder by BoldGrid, published on 20 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52713 in the wild and no public exploit code.

Affected product: Post and Page Builder by BoldGrid. 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-52713/ (Markdown: https://insights.sbomify.com/CVE-2025-52713/index.md)
```

## Sources

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

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