LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48744: WordPress Availability Calendar Plugin <= 1.2.6 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Offshore Web Master Availability Calendar allows Cross Site Request Forgery.This issue affects Availability Calendar: from n/a through 1.2.6.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-48744 is a CSRF flaw in the WordPress Availability Calendar plugin through version 1.2.6. A remote attacker could potentially cause a logged-in user’s browser to perform unintended plugin actions, creating limited integrity and availability risk. The sources do not state active exploitation or a confirmed fixed version.

Executive priority

Treat this as a moderate WordPress plugin risk. It is not known to be exploited from the provided evidence, but internet-facing WordPress sites with affected plugin versions should be reviewed and remediated during normal vulnerability maintenance.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in Offshore Web Master Availability Calendar. CVSS 3.1 is 5.4: network-reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, and low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites running the Availability Calendar plugin, package name availability-calendar, at versions through 1.2.6. The CVE source bundle provides no CPEs, so asset matching depends on WordPress plugin inventory rather than platform CPE scanning.

Exploitation context

CISA KEV status is false, and the provided sources do not report active exploitation. Practical abuse would require persuading a logged-in site user with relevant access to interact with attacker-controlled content while authenticated to the affected WordPress site.

Researcher notes

The public bundle lacks endpoint details, affected actions, proof-of-concept material, and fix version. Validation should stay defensive: confirm plugin presence, version, and vendor advisory status. Do not assume broader WordPress impact beyond Offshore Web Master Availability Calendar through 1.2.6.

Mitigation direction

  • Inventory WordPress sites for the availability-calendar plugin and version.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • Disable or remove the plugin where it is unused or unmaintained.
  • Restrict privileged WordPress access to trusted administrators only.
  • Prioritize remediation on externally administered or business-critical WordPress sites.

Validation and detection

  • Confirm installed plugin slug is availability-calendar.
  • Verify plugin version is 1.2.6 or earlier.
  • Review WordPress audit logs for unexpected calendar or plugin configuration changes.
  • Check whether vendor guidance identifies a patched version.
  • Confirm compensating controls do not rely on missing CSRF protection.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-48744 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-48744Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Offshore Web MasterAvailability Calendaravailability-calendar, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.