dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-22703

HIGH · 7.1 CVSS v3.1 Published 2025-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in manuelvicedo Forge – Front-End Page Builder forge allows Stored XSS.This issue affects Forge – Front-End Page Builder: from n/a through <= 1.4.6.

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

CSRF vulnerability in the Forge Page Builder plugin enables attackers to trick authenticated administrators into unknowingly submitting requests that inject persistent malicious JavaScript (Stored XSS) into pages built with the plugin. This affects all versions up to and including 1.4.6.

MitigationImplement anti-CSRF tokens on all state-changing forms and AJAX endpoints, combined with proper input validation and output encoding to prevent the XSS execution. Update to the patched version once released.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Forge Page Builder is installed
    Locate the plugin in your CMS plugin directory or check the plugin management interface for 'Forge Page Builder' or similar naming
    Affected if The plugin is not found in the system
  2. Check installed version
    Access the plugin details page in your CMS admin panel or inspect the plugin's main PHP file for the version declaration
    Affected if The version is 1.4.6 or lower
  3. Confirm plugin is active
    Check the plugins list in the admin panel to see if Forge Page Builder is enabled
    Affected if Plugin is active and running
  4. Inspect form submissions for CSRF protection
    Examine the page builder's form HTML source (particularly those saving page content) to determine if a CSRF token field is present
    Affected if No CSRF token field is found in state-changing forms
  5. Review saved pages for unexpected scripts
    Use the admin panel to view the HTML source of pages created with the plugin, looking for script tags that were not intentionally added
    Affected if Unexpected JavaScript code is present in page content

You are affected if Forge Page Builder is installed, active, and running version 1.4.6 or lower without CSRF protection on its forms.

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

Implement anti-CSRF tokens on all state-changing forms and AJAX endpoints, combined with proper input validation and output encoding to prevent the XSS execution. Update to the patched version once released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22703 — 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-22703 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