Wp Ical AvailabilityWordPress extension · Wpicalavailability
CVE-2023-41853
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 WP iCal Availability plugin <= 1.0.3 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 WP iCal Availability WordPress plugin versions 1.0.3 and below allows attackers to induce authenticated users to perform unwanted actions, such as modifying plugin settings or data, by tricking them into submitting 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
Wp Ical AvailabilityWordPress extension
<= 1.0.3CVSS 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.
-
Check if WP iCal Availability plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP iCal Availability' or check the plugin files in /wp-content/plugins/wp-ical-availability/ for version information in the main plugin file headerAffected if Plugin is installed and version is 1.0.3 or below
-
Identify the exact plugin versionOpen the main plugin file (usually wp-ical-availability.php) and look for the 'Version' header in the plugin comment block, or check the plugin metadata via WordPress admin plugin listAffected if Version displayed is 1.0.3 or lower
-
Verify if state-changing operations lack CSRF protectionInspect the plugin's PHP files for form submissions and AJAX actions that modify data (settings, availability, etc.). Look for the absence of wp_verify_nonce() or check_admin_referer() calls before processing POST/GET requests that change stateAffected if Forms or AJAX handlers that modify plugin data do not verify nonces or referer headers before processing requests
-
Check for SameSite cookie attributesReview the plugin's cookie handling code or session management to see if cookies set by the plugin include the SameSite attribute, or test by inspecting cookie headers in browser dev tools when logged into WordPressAffected if Cookies related to the plugin are missing SameSite=Strict or SameSite=Lax attributes
You are affected if the WP iCal Availability plugin version 1.0.3 or below is installed and the plugin processes state-changing requests without validating anti-CSRF nonces or verifying request origins.
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 (nonces) on all state-changing operations, verify Referer/Origin headers, and add SameSite cookie attributes. Update to a patched version if available.
Fix this in Wp Ical Availability
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41853 — 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-41853 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