dbcve.org
Easy AppointmentsWordPress extension

CVE-2022-36424

HIGH · 8.8 CVSS v3.1 Published 2023-07-17
Fix available
A fix is available. Upgrade to after 3.11.9 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 Nikola Loncar Easy Appointments plugin <= 3.11.9 versions.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Easy Appointments plugin by Nikola Loncar affecting versions 3.11.9 and below. The flaw allows attackers to trick authenticated administrators into performing unintended administrative actions through maliciously crafted requests.

MitigationUpdate the Easy Appointments plugin to the latest patched version immediately. Additionally, implement anti-CSRF tokens and SameSite cookie attributes on sensitive WordPress admin actions to prevent future CSRF attacks.

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:<= 3.11.9

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. Confirm Easy Appointments plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'easy-appointments' or check the Plugins page in WordPress admin for Easy Appointments in the list of installed plugins.
    Affected if The plugin is not found in the installed plugins list or directory.
  2. Identify the installed version of Easy Appointments
    Open the main plugin file (usually easy-appointments/easy-appointments.php) and look for the 'Version:' header in the plugin comment block, or check the plugin details in WordPress admin under Plugins > Installed Plugins.
    Affected if The version listed is 3.11.9 or any version lower than 3.11.9.
  3. Verify admin access is enabled
    CSRF attacks require an authenticated administrator session. Confirm that the WordPress site has administrator accounts and the Easy Appointments plugin admin interface is accessible.
    Affected if Administrator accounts exist and the plugin admin panel is reachable.
  4. Check for anti-CSRF protections in admin actions
    Inspect the Easy Appointments plugin source code for the presence of nonce tokens or SameSite cookie attributes on admin action handlers. Look for wp_verify_nonce or check_admin_referer calls in form submissions and AJAX handlers.
    Affected if No nonce verification or SameSite cookie attributes are found in the plugin's admin action handlers.

If Easy Appointments version 3.11.9 or lower is installed and the plugin admin interface is accessible without proper CSRF protections, the environment is affected by this vulnerability.

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 3.11.9
Interim mitigation

Update the Easy Appointments plugin to the latest patched version immediately. Additionally, implement anti-CSRF tokens and SameSite cookie attributes on sensitive WordPress admin actions to prevent future CSRF attacks.

Recommended fix Moderate confidence

latest version available in WordPress plugin repository (greater than 3.11.9)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find the Easy Appointments plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the plugin was updated successfully by checking the version number
  6. 6. Test the appointment booking functionality to ensure the plugin works correctly after the update

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

Fix this in Easy Appointments Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36424 — 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-2022-36424 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