LiveActive security incident?Get immediate response
CVE Record

CVE-2023-7115: PageLayer < 1.8.1 - Admin+ Stored XSS

The Page Builder: Pagelayer WordPress plugin before 1.8.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-7115 is a stored cross-site scripting flaw in the Page Builder: Pagelayer WordPress plugin before 1.8.1. A high-privilege user, such as an administrator, could save unsafe script content in plugin settings even where WordPress normally blocks unfiltered HTML, such as multisite setups.

Executive priority

Prioritize normal patching for affected WordPress sites, especially multisite environments. The vulnerability requires high privileges, so urgency is below unauthenticated flaws, but it can weaken administrative safety controls and create persistent browser-side risk.

Technical view

The issue is CWE-79 caused by missing sanitization and escaping of some Pagelayer settings. The CVSS 3.1 score is 4.8, with network access, low attack complexity, high privileges required, user interaction required, changed scope, and limited confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress sites using Page Builder: Pagelayer versions before 1.8.1. The most relevant business scenario is multisite or hardened WordPress environments that rely on disabling unfiltered_html for administrators or other high-privilege users.

Exploitation context

The bundled WPScan reference is tagged as an exploit entry, but the source bundle does not show active exploitation, and CISA KEV status is false. Treat this as a credible stored XSS issue, not as evidence of in-the-wild exploitation.

Researcher notes

The source data identifies Page Builder: Pagelayer before 1.8.1 and does not provide broader product or CPE detail. The key security boundary is WordPress environments where admins should not be able to store unfiltered HTML. Avoid assuming unauthenticated or low-privilege exploitability.

Mitigation direction

  • Update Page Builder: Pagelayer to version 1.8.1 or later.
  • Review vendor and plugin guidance for any additional remediation steps.
  • Restrict administrator access to trusted users only.
  • Audit multisite roles where unfiltered_html is intentionally disabled.
  • Review recently changed Pagelayer settings or content for unexpected scripts.

Validation and detection

  • Inventory WordPress sites for Page Builder: Pagelayer installations.
  • Confirm each installation is running version 1.8.1 or later.
  • Check whether affected sites use multisite or hardened HTML restrictions.
  • Review plugin settings changed by high-privilege users before remediation.
  • Monitor affected sites for unexpected stored script behavior.
Prepared
Confidence
medium
Sources
3

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 · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-7115 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
4.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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
2Source 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
4.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N1.72.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownPage Builder: Pagelayer0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.