Appointment CalendarWordPress extension · Apointzilla
CVE-2023-46198
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Scientech It Solution Appointment Calendar plugin <= 2.9.6 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Scientech It Solution Appointment Calendar WordPress plugin versions 2.9.6 and below allows attackers to induce authenticated users to perform unintended actions via malicious requests.
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
Appointment CalendarWordPress extension
<= 2.9.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Apointzilla Appointment Calendar pluginIn WordPress admin, go to Plugins > Installed Plugins and look for 'Apointzilla Appointment Calendar' or 'Scientech It Solution Appointment Calendar'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'apointzilla' or similar.Affected if Plugin is installed and active
-
Identify the installed versionIn WordPress admin_plugins page, find the plugin and read the version number displayed under the plugin name. Alternatively, check the main plugin PHP file header for 'Version:' tag.Affected if Version is 2.9.6 or lower
-
Check if state-changing forms include CSRF tokensInspect the HTML source of any frontend or admin forms generated by the plugin (appointment submission, settings changes, calendar configuration). Look for hidden input fields with names like 'nonce', 'token', 'csrf', or similar security tokens within the <form> tags.Affected if Forms lack hidden CSRF token fields or do not include nonce verification in the form action handlers
-
Verify referrer header validation in plugin codeExamine the plugin's PHP files handling form submissions (usually in main plugin file or handlers). Search for code that checks $_SERVER['HTTP_REFERER'] or validates request origin before processing state-changing operations.Affected if No referrer header validation exists in form processing logic
-
Confirm SameSite cookie attributes are absentCheck the plugin's cookie-setting code (session handling, authentication). Look for 'setcookie' or 'Set-Cookie' calls and verify if the 'SameSite' attribute is set to 'Strict' or 'Lax'.Affected if Cookies are set without SameSite attribute or without secure flags
User is affected if Apointzilla Appointment Calendar plugin version 2.9.6 or lower is installed and active, and the plugin handles state-changing operations (form submissions, settings changes) without CSRF token validation, referrer checking, or SameSite cookie protections.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement anti-CSRF tokens or unique request identifiers for state-changing operations in the plugin; verify request origin via proper referrer header validation or SameSite cookie attributes.
Fix this in Appointment Calendar
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-46198 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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