Skip to main content
← Vulnerabilities

MapPress Maps for WordPress < 2.97.15 - Unauthenticated Email Address Disclosure

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Published
Last modified
Published
Not listed in CISA KEV
15/100 · provisional
Unclear
Fix
Fixed in 2.97.15
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

The MapPress Maps plugin for WordPress is affected. Unauthenticated visitors can exploit it to obtain the email addresses and display names of users on the site, exposing personal information.

Read the original description

The MapPress WordPress plugin before 2.97.15 does not restrict which user's data its front-end map embed handler renders, allowing unauthenticated visitors to retrieve the email address and display name of any user on the site by enumerating user IDs.

What to do

  • Upgrade to a fixed version: 2.97.15.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • Unknown MapPress

    fixed in 2.97.15

Evidence 1

  1. Exploit

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-118168

What does this mean?

Unauthenticated visitors can retrieve the email address and display name of any user on the site by enumerating user IDs. No login is needed to request this data.Source: wpscan.com

Am I affected, and how do I check?

MapPress Maps for WordPress (plugin slug mappress-google-maps-for-wordpress) versions before 2.97.15 are in scope. To check a site, look at the plugin version shown on the Plugins screen in the WordPress admin.Source: wpscan.com

What should I do about it?

Update the MapPress Maps for WordPress plugin to version 2.97.15 or later, which is the listed fixed version.Source: wpscan.com

Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data