LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46190: WordPress Novo-Map : your WP posts on custom google maps Plugin <= 1.1.2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Novo-media Novo-Map : your WP posts on custom google maps plugin <= 1.1.2 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF flaw in the WordPress Novo-Map plugin. An attacker would need to trick an authenticated user into taking an unintended browser action. The documented impact is limited integrity change, not data theft or service outage.

Executive priority

Treat this as a moderate WordPress hygiene item. It is not described as actively exploited, but it can allow unauthorized changes if a logged-in user is tricked. Remediate during the next maintenance window, sooner for business-critical sites.

Technical view

CVE-2023-46190 is CWE-352 affecting Novo-media Novo-Map: your WP posts on custom google maps plugin versions <= 1.1.2. CVSS 3.1 is 4.3, with network reachability, low complexity, no attacker privileges, required user interaction, and low integrity impact.

Likely exposure

Exposure is limited to WordPress sites that have the Novo-Map plugin installed, especially version 1.1.2 or older. The bundle provides no CPEs and lists packageName as novo-map, so plugin inventory is the key check.

Exploitation context

The source bundle does not identify active exploitation, and KEV is false. Exploitation requires user interaction, likely involving a logged-in WordPress user being induced to perform an unintended request. No exploit details are provided in the sources.

Researcher notes

Evidence is concise. The CVE description and Patchstack reference identify CSRF in plugin versions <= 1.1.2. The CVSS vector limits impact to integrity and requires user interaction. No patch version, exploit status, or detailed vulnerable action is included in the bundle.

Mitigation direction

  • Inventory WordPress sites for the Novo-Map plugin and record installed versions.
  • Update, disable, or remove the plugin according to vendor or Patchstack guidance.
  • Prioritize sites where administrators access WordPress from unmanaged or high-risk browsers.
  • Remind admins not to click untrusted links while authenticated to WordPress.

Validation and detection

  • Confirm whether Novo-Map is installed and whether the version is <= 1.1.2.
  • Check WordPress plugin records across production, staging, and archived sites.
  • Review administrative settings or content affected by the plugin for unexpected changes.
  • Verify remediation by confirming the vulnerable plugin version is no longer present.
Prepared
Confidence
medium
Sources
3

Public sources used

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-46190 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-2023-46190Attack 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Novo-mediaNovo-Map : your WP posts on custom google mapsnovo-map, n/aunaffected
Weakness

CWE details

CWE-352

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.

Open CWE intelligenceSame-CWE CVEs