LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31577: WordPress Appointify plugin <= 1.0.8 - Arbitrary File Upload vulnerability

Unrestricted Upload of File with Dangerous Type vulnerability in appointify Appointify appointify allows Upload a Web Shell to a Web Server.This issue affects Appointify: from n/a through <= 1.0.8.

MediumCVSS 6.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31577 affects the WordPress Appointify plugin through version 1.0.8. A highly privileged user could upload a dangerous file type, potentially including a web shell. That can turn a plugin issue into server-side compromise, but the published scoring requires high privileges and there is no cited evidence of active exploitation.

Executive priority

Treat as a moderate-priority WordPress plugin risk. Prioritize externally reachable WordPress sites, sites handling sensitive data, and environments with many privileged users. Absence from KEV lowers urgency, but web shell impact warrants timely validation and mitigation.

Technical view

The issue is CWE-434 unrestricted upload of a dangerous file type in Appointify <=1.0.8. CVSS 3.1 score is 6.6 with AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L. The source description says the flaw allows uploading a web shell to a web server.

Likely exposure

Exposure is limited to WordPress sites running the Appointify plugin at version 1.0.8 or earlier. Risk is higher where administrator or other high-privilege WordPress accounts are shared, weakly protected, or suspected compromised.

Exploitation context

The CVE is not listed as KEV in the provided bundle. The sources do not cite active exploitation. The vulnerability still matters because a successful high-privilege upload could enable unauthorized server-side code execution through a web shell.

Researcher notes

The public bundle names the vulnerable product and version range, CWE-434, CVSS vector, and web shell impact. It does not provide exploit evidence, detailed vulnerable endpoint information, patch status, or vendor remediation steps, so validation should remain non-invasive and source-grounded.

Mitigation direction

  • Inventory WordPress sites for Appointify plugin versions <=1.0.8.
  • Check Appointify or Patchstack guidance for a fixed version or mitigation.
  • Disable Appointify where it is not business-critical until guidance is applied.
  • Restrict privileged WordPress access and enforce MFA for administrator accounts.
  • Review upload controls and block executable file types where supported.

Validation and detection

  • Confirm whether Appointify is installed on each WordPress site.
  • Record the installed Appointify version and compare it with <=1.0.8.
  • Review privileged WordPress accounts with plugin or upload access.
  • Inspect recent uploads for unexpected executable or script-like files.
  • Review web server logs for unusual privileged upload activity.
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-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-31577 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.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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
6.6CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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
appointifyAppointifyappointify, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.