dbcve.org
Easy\!appointmentsWordPress extension · Easyappointments

CVE-2025-31828

HIGH · 8.8 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to after 1.4.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in alextselegidis Easy!Appointments easyappointments allows Cross Site Request Forgery.This issue affects Easy!Appointments: from n/a through <= 1.4.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in Easy!Appointments allows remote attackers to trick authenticated users into executing unwanted state-changing actions (such as modifying appointments, user settings, or administrative changes) by leveraging the trust relationship between the browser and the application.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing form submissions and validate Origin/Referer headers server-side to ensure requests originate from legitimate sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Easy\!appointmentsWordPress extension
Affected:<= 1.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Easy!Appointments version
    Locate the version file, footer, or admin panel information page that displays the current software version. Common locations include a version.php file, config file, or the application footer.
    Affected if The installed version is 1.4.2 or any earlier version.
  2. Inspect state-changing forms for anti-CSRF tokens
    Log in as an authenticated user and examine the HTML source of forms that perform state-changing actions (appointment creation, user settings, admin functions). Look for hidden input fields containing tokens (commonly named _token, csrf_token, or similar) in forms that submit via POST.
    Affected if State-changing forms lack hidden CSRF token fields or the tokens are not being validated server-side.
  3. Verify CSRF token validation server-side
    If you have access to the backend code, search for CSRF validation logic in the request handling controllers. Check that tokens submitted in forms are being validated against stored session values before processing state-changing operations.
    Affected if No server-side validation of CSRF tokens exists in the request handlers for state-changing actions.
  4. Check for Origin or Referer header validation
    Examine the application's request handling code to determine if the Origin or Referer HTTP headers are validated server-side to ensure requests originate from legitimate domains.
    Affected if The application does not validate Origin or Referer headers to confirm request origin.

You are affected if Easy!Appointments version 1.4.2 or earlier is installed AND state-changing forms lack anti-CSRF token protection or server-side validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.4.2
Interim mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing form submissions and validate Origin/Referer headers server-side to ensure requests originate from legitimate sources.

Recommended fix Moderate confidence

1.4.3 or later

  1. 1. Back up your current Easy!Appointments installation and database before upgrading.
  2. 2. Download the latest version of Easy!Appointments from the official repository (github.com/alextselegidis/easyappointments).
  3. 3. Review the upgrade instructions provided in the project documentation or release notes.
  4. 4. Replace the existing installation files with the new version, preserving your configuration and data.
  5. 5. Verify that the application functions correctly after the upgrade.
  6. 6. Test that CSRF protection is working by confirming that POST/PUT/DELETE requests require valid anti-CSRF tokens.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Easy\!appointments Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31828 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31828 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data