LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6524: MapPress Maps for WordPress <= 2.88.13 - Authenticated (Contributor+) Stored Cross-Site Scripting

The MapPress Maps for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the map title parameter in all versions up to and including 2.88.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with contributor access or higher to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress site using MapPress Maps up to version 2.88.13 can let a logged-in contributor plant script in a map title. That script can run for visitors who open the affected page, creating account, content, or session risk depending on who views it.

Executive priority

Schedule remediation in the normal vulnerability cycle, faster for multi-author or client-managed WordPress sites. The issue is not critical, but stored XSS can become high-impact if privileged users or administrators view affected pages.

Technical view

CVE-2023-6524 is authenticated stored cross-site scripting in the MapPress Maps for WordPress map title parameter. The reported cause is insufficient input sanitization and output escaping. CVSS 3.1 is 6.4 with low privileges required, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress installations running MapPress Maps for WordPress version 2.88.13 or earlier, especially sites with Contributor or higher users who are not fully trusted. Single-admin sites have lower practical exposure.

Exploitation context

The provided sources describe authenticated Contributor+ stored XSS. The bundle says it is not in KEV, and no provided source states active exploitation. Treat exploitation as plausible where untrusted authors can create or edit map content.

Researcher notes

The strongest evidence is Wordfence’s advisory, the CVE record, and the WordPress plugin Trac changeset. The source bundle does not provide proof of exploitation or a clearly named fixed version, so remediation should be tied to vendor-confirmed release guidance.

Mitigation direction

  • Identify all WordPress sites using MapPress Maps for WordPress.
  • Check vendor, WordPress plugin, or Wordfence guidance for the fixed release.
  • Upgrade from versions 2.88.13 or earlier when a vendor-confirmed fixed version is available.
  • Restrict Contributor or higher access to trusted users only.
  • Review existing map titles and affected pages for suspicious script content.

Validation and detection

  • Inventory plugin versions across production and staging WordPress sites.
  • Confirm whether any installation is running version 2.88.13 or earlier.
  • Review WordPress accounts with Contributor, Author, Editor, or Administrator roles.
  • Inspect recent MapPress map title changes by non-administrators.
  • Verify sanitized and escaped map title rendering in a safe staging environment.
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 · 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-6524 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
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
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
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
chrisvrichardsonMapPress Maps for WordPress0unaffected
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.