LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30544: WordPress OSM – OpenStreetMap Plugin <= 6.0.1 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) in MiKa's OSM – OpenStreetMap plugin <= 6.0.1 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the WordPress OSM – OpenStreetMap plugin, reported for versions up to 6.0.1. It is a CSRF flaw: a targeted user could be tricked into making an unwanted site change. The public record rates it medium, with limited integrity impact and no evidence here of active exploitation.

Executive priority

Treat as a scheduled remediation item, not an emergency, unless the plugin is used on sensitive or heavily administered WordPress sites. Prioritize inventory first because exposure depends on a specific plugin and version.

Technical view

CVE-2022-30544 is CWE-352 Cross-Site Request Forgery in MiKa's OSM – OpenStreetMap WordPress plugin. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, and low integrity impact. The bundle does not identify a specific endpoint, fixed version, or exploit details.

Likely exposure

Exposure is most likely on WordPress sites with the OSM – OpenStreetMap plugin installed at version 6.0.1 or earlier. Sites without this plugin are not indicated as exposed. The provided affected-version metadata is limited, so inventory confirmation matters.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle. The available sources support a CSRF issue requiring user interaction, but do not provide evidence of active exploitation, public exploit availability, or weaponized campaigns.

Researcher notes

The source bundle lacks endpoint-level detail, fixed-version metadata, and exploitation evidence. Validation should focus on asset inventory, version confirmation, and vendor advisory review rather than attempting offensive reproduction.

Mitigation direction

  • Inventory WordPress sites for the OSM – OpenStreetMap plugin and record installed versions.
  • Check vendor or Patchstack guidance for the fixed version before changing production systems.
  • Update the plugin if an official fixed release is available.
  • Disable or remove the plugin where it is unused or cannot be safely updated.
  • Limit administrative sessions and review WordPress anti-CSRF protections around plugin settings.

Validation and detection

  • Confirm whether each WordPress site has the OSM – OpenStreetMap plugin installed.
  • Compare installed versions against the reported vulnerable range: 6.0.1 or earlier.
  • Review plugin release notes or vendor advisories for remediation status.
  • Check change logs and admin activity for unexpected plugin configuration changes.
  • Document whether mitigation was update, removal, or accepted risk.
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-352: 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-2022-30544 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
MiKaOSM – OpenStreetMapn/aunaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.