LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45645: WordPress WP Open Street Map Plugin <= 1.25 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in InfoD74 WP Open Street Map plugin <= 1.25 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-45645 is a CSRF issue in the WP Open Street Map WordPress plugin version 1.25 and earlier. An attacker may be able to trick a user into triggering unintended plugin-related changes. The cited records rate it medium severity, with limited integrity and availability impact and no confidentiality impact.

Executive priority

Treat as a moderate-priority WordPress plugin issue. Prioritize internet-facing business sites and sites with many privileged users. It is not listed as known exploited in the provided data, but remediation should be scheduled with normal plugin maintenance because CSRF can cause unauthorized operational changes.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in InfoD74 WP Open Street Map <= 1.25. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, low integrity impact, and low availability impact. The bundle does not include endpoint, nonce, or fixed-version details.

Likely exposure

Exposure is limited to WordPress sites using the InfoD74 WP Open Street Map plugin at version 1.25 or earlier. The source bundle provides the package slug wp-open-street-map, but no CPEs and no detailed fixed-version metadata.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires user interaction and likely depends on a victim visiting attacker-controlled content while authenticated to WordPress. The exact vulnerable action is not described in the supplied sources.

Researcher notes

Evidence is sparse. The CVE and Patchstack entry identify the vulnerability class, affected plugin, affected version boundary, and CVSS vector, but not the vulnerable request, required victim role, proof of concept, patch version, or workaround. Avoid asserting exploitability details beyond the published vector.

Mitigation direction

  • Inventory WordPress sites for the wp-open-street-map plugin.
  • Check installed plugin versions against the <= 1.25 affected range.
  • Update or remove the plugin following vendor or Patchstack guidance.
  • Limit WordPress administrative privileges until remediation is complete.
  • Monitor vendor advisories for fixed-version or workaround details.

Validation and detection

  • Confirm whether each WordPress site has WP Open Street Map installed.
  • Record the plugin version and flag versions 1.25 or earlier.
  • Review change logs or advisories for vendor-confirmed fixes.
  • Check logs for unexpected plugin configuration changes.
  • Validate CSRF protections only in authorized test environments.
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-2023-45645 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
5.4 (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:L

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

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-45645Attack 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:L

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
InfoD74WP Open Street Mapwp-open-street-map, n/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.