LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6738: PageLayer <= 1.7.8 - Authenticated(Contributor+) Stored Cross-Site Scripting via meta fields

The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'pagelayer_header_code', 'pagelayer_body_open_code', and 'pagelayer_footer_code' meta fields in all versions up to, and including, 1.7.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This appears to be a reintroduction of a vulnerability patched in version 1.7.7.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-6738 affects the Pagelayer WordPress page builder. A logged-in contributor or higher user could store malicious browser script in Pagelayer page meta fields. That script runs when someone opens the affected page. The main risk is account or visitor browser compromise through a trusted site page.

Executive priority

Treat this as a moderate-priority WordPress application risk. It is most urgent for public, multi-author, agency-managed, or customer-administered sites because a low-privileged account can create persistent browser-side impact.

Technical view

Pagelayer versions up to and including 1.7.8 insufficiently sanitize and escape pagelayer_header_code, pagelayer_body_open_code, and pagelayer_footer_code meta fields. The result is authenticated stored cross-site scripting with contributor-level privileges or higher. Sources indicate this may reintroduce an issue previously patched in 1.7.7.

Likely exposure

Exposure is likely limited to WordPress sites running Pagelayer through version 1.7.8 where contributor-level or higher accounts exist, especially multi-author sites or sites with compromised editor accounts.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not show active exploitation. Attackers need authenticated contributor-or-higher access, but stored XSS can affect later page visitors without additional attacker interaction.

Researcher notes

The source bundle identifies CWE-20 and CVSS 3.1 score 5.4. The vulnerable fields are explicitly named, and WordPress Trac references show relevant code and a 1.7.8-to-1.7.9 changeset. Evidence for exploitation in the wild is not provided.

Mitigation direction

  • Upgrade Pagelayer to a vendor-fixed release newer than 1.7.8.
  • Restrict contributor-level and higher WordPress accounts to trusted users only.
  • Review Pagelayer pages for unexpected header, body-open, or footer code.
  • Remove unnecessary authoring privileges from dormant or shared accounts.
  • Check vendor guidance for any additional cleanup or hardening steps.

Validation and detection

  • Inventory WordPress sites using the Pagelayer plugin.
  • Confirm whether installed Pagelayer versions are 1.7.8 or older.
  • Review users with contributor-level or higher permissions.
  • Inspect affected meta fields for unexpected scripts or unfamiliar code.
  • Confirm updated sites no longer accept unsafe stored meta content.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-6738 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-6738Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
softaculousPage Builder: Pagelayer – Drag and Drop website builder0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.