dbcve.org
Path TraversalWeakness · CWE-22

CVE-2023-46784

HIGH · 8.2 CVSS v3.1 Published 2024-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), Server-Side Request Forgery (SSRF) vulnerability in Room 34 Creative Services, LLC ICS Calendar ics-calendar allows Absolute Path Traversal, : Server Side Request Forgery.This issue affects ICS Calendar: from n/a through 10.12.0.3.

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

The ICS Calendar WordPress plugin versions up to 10.12.0.3 contains both an Absolute Path Traversal vulnerability allowing attackers to access files outside restricted directories, and a Server-Side Request Forgery (SSRF) vulnerability enabling the server to make unintended network requests. These flaws can be exploited to read sensitive files from the server filesystem or probe internal network resources.

MitigationUpdate the ICS Calendar plugin to a version beyond 10.12.0.3 when available; if no patched version exists, implement strict input validation on all user-supplied paths and URLs, restrict file system permissions, and consider deploying a WAF to block traversal sequences and suspicious outbound requests.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

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 ICS Calendar plugin version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate ICS Calendar, and note the version number displayed. Alternatively, inspect the plugin's main PHP file (typically ics-calendar.php) in wp-content/plugins/ics-calendar/ and look for the 'Version' header in the plugin comment block.
    Affected if The displayed version is 10.12.0.3 or any earlier version (e.g., 10.12.0, 10.11.0, 10.0.0).
  2. Confirm the plugin is active
    In the WordPress plugins admin page, verify that ICS Calendar shows as 'Active' rather than 'Inactive' or 'Must Use'. An inactive plugin cannot be exploited.
    Affected if The plugin is active and running.
  3. Check for external-facing plugin features
    Review the ICS Calendar settings page in the WordPress admin (Settings > ICS Calendar or similar) and inspect the public-facing calendar pages where the plugin is embedded via shortcode (commonly [ics_calendar] or [calendar]). Determine if the plugin is configured to fetch external .ics feed URLs.
    Affected if The plugin is configured with external .ics feed URLs that could be manipulated for SSRF exploitation, or the calendar is publicly accessible.
  4. Review server access logs for suspicious requests
    Examine web server access logs (Apache, Nginx, or WAF logs) for incoming requests to pages containing the ICS Calendar shortcode. Look for unusual URL parameters, especially those containing 'file://', '../', '..\', or unexpected domain names in query strings that may indicate path traversal or SSRF probing.
    Affected if Log entries show requests with traversal sequences (../, ..\) targeting local filesystem paths or unusual URLs pointing to internal network addresses (e.g., 127.0.0.1, 192.168.x.x).

You are affected if the ICS Calendar plugin version is 10.12.0.3 or earlier AND the plugin is active on a public-facing page, as both the path traversal and SSRF vulnerabilities require the plugin to be running to be exploitable.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the ICS Calendar plugin to a version beyond 10.12.0.3 when available; if no patched version exists, implement strict input validation on all user-supplied paths and URLs, restrict file system permissions, and consider deploying a WAF to block traversal sequences and suspicious outbound requests.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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