dbcve.org
Wp Page BuilderWordPress extension · Themeum

CVE-2022-40963

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-18
Fix available
A fix is available. Upgrade to 1.2.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Multiple Auth. (author+) Stored Cross-Site Scripting (XSS) vulnerabilities in WP Page Builder plugin <= 1.2.6 on WordPress.

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

Authenticated (author+) stored cross-site scripting vulnerabilities in WP Page Builder plugin <= 1.2.6 allow malicious JavaScript to be injected and executed in the context of other users' browsers when they view crafted content.

MitigationUpdate WP Page Builder to the latest version and implement proper input sanitization and output encoding for all user-supplied content in plugin fields.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Page BuilderWordPress extension
Affected:< 1.2.7

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Locate WP Page Builder plugin in WordPress
    In the WordPress admin dashboard, go to Plugins > Installed Plugins. Search for 'WP Page Builder' or 'Themeum WP Page Builder' in the plugin list.
    Affected if The plugin is present in the installed plugins list
  2. Identify the installed version number
    Find the version number displayed beneath the plugin name in the plugins list, or check the plugin's main PHP file header for the 'Version' tag.
    Affected if A version number is displayed and can be read
  3. Compare version against the affected range
    Compare the installed version number to the affected range. Version 1.2.7 and later are fixed; versions below 1.2.7 are vulnerable.
    Affected if The installed version is 1.2.6 or lower, indicating the vulnerable release
  4. Confirm plugin is active
    In Plugins > Installed Plugins, verify whether the plugin shows as 'Active' or 'Deactivated'.
    Affected if The plugin is active and processing content on the site

The environment is affected if the WP Page Builder plugin is active and the installed version is 1.2.6 or lower (less than 1.2.7), as this allows authenticated users with author or higher roles to inject malicious scripts into stored content.

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.

dbcve · scoped
Upgrade available Upgrade to 1.2.7 or later
Fixed in 1.2.7
Interim mitigation

Update WP Page Builder to the latest version and implement proper input sanitization and output encoding for all user-supplied content in plugin fields.

Recommended fix High confidence

WP Page Builder version 1.2.7 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Find 'WP Page Builder' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.2.7 or later
  5. 5. Alternatively, download version 1.2.7 from the WordPress plugin repository and upload manually via Plugins > Add New > Upload Plugin
  6. 6. After upgrading, verify the plugin shows version 1.2.7 or higher in the Plugins list
  7. 7. Test that the Page Builder functionality works correctly on your site

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Page Builder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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