LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31602: WordPress Apimo Connector plugin <= 2.6.5.1 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Proptech Plugin Apimo Connector apimo allows Cross Site Request Forgery.This issue affects Apimo Connector: from n/a through <= 2.6.5.1.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31602 is a CSRF issue in the WordPress Apimo Connector plugin. A tricked administrator could unintentionally make a low-impact settings change. The reported severity is medium, with low integrity impact and no confidentiality or availability impact in the provided CVSS data.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It is not documented as exploited, but affected sites should be inventoried and remediated because administrator-driven settings changes can still create business risk.

Technical view

The source bundle describes CWE-352 CSRF in Proptech Plugin Apimo Connector, package apimo, affecting versions through 2.6.5.1. CVSS 3.1 is 4.3: network reachable, low complexity, no privileges required, user interaction required, unchanged scope, integrity low.

Likely exposure

Exposure is likely limited to WordPress sites with Apimo Connector installed at a vulnerable version through 2.6.5.1. The bundle contains incomplete affected-version metadata, so verify plugin presence and exact version locally.

Exploitation context

The bundle does not identify active exploitation, and KEV is false. Exploitation requires user interaction, likely involving an authenticated administrator being induced to perform an unintended settings-changing request.

Researcher notes

Evidence is limited to the CVE bundle and Patchstack reference. The title reports through 2.6.5.1, while the Patchstack URL text mentions 2.6.3.1, so version impact should be confirmed before broad claims.

Mitigation direction

  • Inventory WordPress sites for the Apimo Connector plugin and record installed versions.
  • Check vendor, WordPress.org, and Patchstack guidance for a fixed release before deciding upgrade timing.
  • If the plugin is not required, disable or remove it from affected sites.
  • Restrict administrator sessions and avoid clicking untrusted links while exposure remains.
  • After remediation, review plugin settings for unauthorized changes.

Validation and detection

  • Confirm whether Apimo Connector is installed and whether its version is within the reported affected range.
  • Review administrative settings changes for unexpected Apimo Connector modifications.
  • Verify current plugin code or vendor notes indicate CSRF protections on settings-changing actions.
  • Track Patchstack and CVE updates for clarified affected versions or fixed-release details.
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-2025-31602 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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.4Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2025-31602Attack 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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Proptech PluginApimo Connectorapimo, 0unaffected
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.