dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-52713

MEDIUM · 6.4 CVSS v3.1 Published 2025-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in BoldGrid Post and Page Builder plugin for WordPress allows attackers to make the server perform unintended requests to internal or external resources, potentially accessing internal services, cloud metadata, or pivoting to internal network targets.

MitigationUpdate the BoldGrid Post and Page Builder plugin to the latest version once available. If no update exists, implement URL allowlisting and validate all user-supplied URLs against a strict allowlist of permitted domains/IPs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify BoldGrid Post and Page Builder is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the boldgrid-post-and-page-builder folder
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, find the BoldGrid Post and Page Builder entry in Plugins list and note the version number displayed, or check the plugin header in /wp-content/plugins/boldgrid-post-and-page-builder/boldgrid-post-and-page-builder.php for 'Version:'
    Affected if Version number matches or falls within any affected version range if published
  3. Confirm SSRF-prone feature is accessible
    Check if the plugin URL import, external content fetch, or media embedding features are available to users, typically found in the plugin settings under Post/Page Builder > Settings or during content creation workflow
    Affected if Any feature that accepts and fetches external URLs is enabled and accessible to users or contributors
  4. Review plugin configuration for URL validation settings
    Inspect plugin settings pages for any URL allowlisting or validation options, typically found in WordPress admin under BoldGrid > Configuration or similar
    Affected if No strict allowlist is configured for external URL requests

A WordPress installation is affected if the BoldGrid Post and Page Builder plugin is installed and the version is within the affected range, particularly when URL fetching features are active without strict allowlist controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the BoldGrid Post and Page Builder plugin to the latest version once available. If no update exists, implement URL allowlisting and validate all user-supplied URLs against a strict allowlist of permitted domains/IPs.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52713 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data