CVE-2026-3297
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 · uneditedThe Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Anchor block in versions up to, and including, 2.0.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 · high confidenceThe Pagelayer WordPress plugin's Anchor block lacks proper input sanitization and output escaping, allowing authenticated users with contributor-level permissions or higher to inject malicious JavaScript into page content. This stored XSS executes whenever other users access the compromised pages.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Pagelayer plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Pagelayer' in the list. Note whether it is active or inactive.Affected if Pagelayer plugin is installed and active
-
Check installed Pagelayer versionIn WordPress admin, go to Plugins > Installed Plugins. Click on 'View details' for the Pagelayer plugin to display the version number. Compare this version to the affected range (up to and including 2.0.9).Affected if Installed version is 2.0.9 or lower
-
Identify pages using Anchor blockIn WordPress admin, go to Pages > All Pages. Edit each page and look in the page editor for any Anchor block added via the Pagelayer builder. Alternatively, search the wp_posts database table for content containing 'pagelayer' and anchor-related meta keys in wp_postmeta.Affected if Any page or post contains a Pagelayer Anchor block
-
Inspect Anchor block parameter valuesIf Anchor blocks are found, open the page editor and select each Anchor block to view its settings. Check the 'Anchor ID' or similar parameter field for any unexpected characters such as < > " ' or javascript: prefixes.Affected if Anchor block contains suspicious characters or patterns in the anchor ID field (e.g., <script, javascript:, onload=, onerror=)
-
Review page source for unescaped outputView a published page containing an Anchor block in a browser. Right-click and select 'View Page Source'. Search for the anchor ID value to see if it appears unescaped (e.g., as raw <script> tags rather than <script>).Affected if Anchor ID value renders as raw HTML/JavaScript in the page source
The environment is affected if Pagelayer plugin versions 2.0.9 or below are installed and active, and any published pages contain Anchor blocks with unescaped or malicious anchor ID values.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the Pagelayer plugin to a version newer than 2.0.9 which includes proper sanitization and escaping for the Anchor block. Verify the update in a staging environment before production deployment.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3297 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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