LiveActive security incident?Get immediate response
CVE Record

CVE-2022-47595: WordPress WP Google Maps Plugin <= 9.0.15 is vulnerable to Path Traversal

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WP Go Maps (formerly WP Google Maps) plugin <= 9.0.15 versions.

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-47595 is a path traversal issue in the WP Go Maps WordPress plugin through version 9.0.15. A highly privileged attacker could potentially read sensitive files accessible to the web server. The source bundle does not show integrity, availability, or confirmed active exploitation impact.

Executive priority

Treat as a moderate-priority WordPress plugin exposure. It is not shown as actively exploited, but file disclosure can expose credentials or configuration secrets. Prioritize internet-facing WordPress sites and environments with broad administrator access.

Technical view

The issue is CWE-22 improper pathname restriction in WP Go Maps, formerly WP Google Maps. CVSS 3.1 is 4.9 with network reachability, low complexity, high privileges required, no user interaction, and high confidentiality impact only. Sources identify versions <= 9.0.15 as vulnerable.

Likely exposure

Exposure is limited to WordPress installations running WP Go Maps/wp-google-maps version 9.0.15 or earlier. Risk is higher where many administrators or privileged plugin users exist, because the CVSS vector requires high privileges.

Exploitation context

The bundle does not indicate CISA KEV listing or active exploitation. Based on CVSS, exploitation is network-reachable and does not require user interaction, but it does require high privileges and appears focused on unauthorized file disclosure.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, CWE-22 classification, and Patchstack VDB reference. The bundle does not include exploit details, proof-of-concept status, or a named fixed version, so validation should focus on version inventory and vendor advisory review.

Mitigation direction

  • Inventory WordPress sites for WP Go Maps or wp-google-maps.
  • Check installed plugin versions and flag 9.0.15 or earlier.
  • Update affected installations following WP Go Maps vendor guidance.
  • Restrict WordPress administrator access to trusted users only.
  • Review web server file permissions for unnecessary readable secrets.

Validation and detection

  • Confirm the plugin is absent or newer than the affected range.
  • Verify privileged WordPress accounts are still required and legitimate.
  • Check logs for unusual privileged plugin activity around file access.
  • Document remediation status for each WordPress site.
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-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-47595 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.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/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.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2022-47595Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/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
WP Go MapsWP Go Maps (formerly WP Google Maps)wp-google-maps, n/aunaffected
Weakness

CWE details

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

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.