LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31601: WordPress Appointy Appointment Scheduler plugin <= 4.2.1 - CSRF to Settings Change vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in appointy Appointy Appointment Scheduler appointy-appointment-scheduler allows Cross Site Request Forgery.This issue affects Appointy Appointment Scheduler: from n/a through <= 4.2.1.

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

Security readout for executives and security teams

Plain-English summary

This CVE is a medium-severity CSRF issue in the WordPress Appointy Appointment Scheduler plugin through version 4.2.1. It could let an attacker cause unauthorized settings changes, affecting integrity and availability. The provided sources do not show active exploitation or name a fixed version.

Executive priority

Treat as a moderate WordPress plugin risk. Prioritize sites using Appointy Appointment Scheduler, especially public business sites where appointment settings affect customer workflows or availability.

Technical view

CVE-2025-31601 is CWE-352 in appointy-appointment-scheduler for WordPress, described as CSRF to settings change. CVSS 3.1 is 6.5, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L. Affected scope is stated as Appointy Appointment Scheduler through <=4.2.1.

Likely exposure

Exposure is limited to WordPress sites with the Appointy Appointment Scheduler plugin installed, especially versions <=4.2.1. Sites not using this plugin are not exposed based on the provided sources.

Exploitation context

The CVE is not marked KEV, and the source bundle provides no evidence of active exploitation. The public description confirms CSRF leading to settings changes but does not provide operational attack details.

Researcher notes

Evidence is sparse. The description says affected through <=4.2.1, while the structured affected entry lists version '0' with defaultStatus unaffected. Do not infer a fixed version from this bundle.

Mitigation direction

  • Inventory WordPress sites for the appointy-appointment-scheduler plugin.
  • Check whether installed versions are <=4.2.1.
  • Review vendor, WordPress, or Patchstack guidance for a fixed release.
  • If no fix is available, consider disabling the plugin until guidance is confirmed.
  • Restrict administrative access and monitor plugin settings for unexpected changes.

Validation and detection

  • Confirm plugin presence and version across WordPress estates.
  • Compare installed versions against the <=4.2.1 affected range.
  • Review Appointy plugin settings for unauthorized or unexpected changes.
  • Check WordPress admin audit logs, if available, for suspicious settings updates.
  • Track vendor and Patchstack advisories for fixed-version confirmation.
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-2025-31601 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
6.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2025-31601Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
appointyAppointy Appointment Schedulerappointy-appointment-scheduler, 0unaffected
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