LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31617: WordPress PostmarkApp Email Integrator plugin <= 2.4 - CSRF to Stored XSS vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Gagan Deep Singh PostmarkApp Email Integrator postmarkapp-email-integrator allows Cross Site Request Forgery.This issue affects PostmarkApp Email Integrator: from n/a through <= 2.4.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the WordPress PostmarkApp Email Integrator plugin through version 2.4. The public record describes a CSRF issue, with the title indicating CSRF leading to stored XSS. An attacker would need user interaction, typically from an authenticated site administrator, but successful abuse could affect confidentiality, integrity, and availability at a limited level.

Executive priority

Treat this as a high-priority WordPress plugin exposure if the plugin is deployed. Prioritize inventory and containment first because the supplied sources do not name a confirmed fix.

Technical view

CVE-2025-31617 is a CWE-352 CSRF vulnerability in postmarkapp-email-integrator <=2.4 with CVSS 3.1 score 7.1. The vector is network reachable, low complexity, no attacker privileges, user interaction required, and changed scope. The bundle does not provide endpoint-level details, proof, or a named fixed version.

Likely exposure

Exposure is limited to WordPress sites running PostmarkApp Email Integrator version 2.4 or earlier. The bundle does not identify other affected products or hosted services.

Exploitation context

CISA KEV status is false, and the supplied sources do not report active exploitation. Practical abuse likely depends on tricking a privileged WordPress user into taking an action while authenticated.

Researcher notes

The source bundle is sparse: it confirms CVE metadata, affected version range, CWE-352, CVSS, and Patchstack reference, but not root cause, vulnerable parameters, exploit maturity, or remediation version. Avoid asserting active exploitation or a patch without additional vendor evidence.

Mitigation direction

  • Inventory WordPress sites for postmarkapp-email-integrator versions <=2.4.
  • Check vendor or Patchstack guidance for a fixed version or official mitigation.
  • Disable or remove the plugin if it is not business-critical.
  • Limit WordPress administrator access to trusted networks where feasible.
  • Monitor for unexpected plugin configuration or content changes.

Validation and detection

  • Confirm whether the plugin is installed and enabled on each WordPress site.
  • Record the installed plugin version and compare it to <=2.4.
  • Review administrative change logs for unexplained plugin or content updates.
  • Check whether official vendor guidance names a patched release.
  • Confirm compensating controls cover CSRF and stored XSS 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-2025-31617 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-31617Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
Gagan Deep SinghPostmarkApp Email Integratorpostmarkapp-email-integrator, 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.