Security readout for executives and security teams
Plain-English summary
A WordPress Availability Calendar plugin flaw can let an attacker trick a user into causing stored malicious script content. If a vulnerable site uses version 0.2.4 or earlier, the issue could affect confidentiality, integrity, and availability at limited levels.
Executive priority
Treat this as a high-priority WordPress plugin exposure for sites using Availability Calendar. It is not listed as known exploited in the provided data, but stored XSS impact warrants prompt inventory, removal, update, or replacement decisions.
Technical view
CVE-2025-46528 is a CWE-352 CSRF issue in Steve Availability Calendar, reported to allow stored XSS. The CVSS 3.1 score is 7.1 with network attack vector, low complexity, no privileges required, and user interaction required. Sources identify affected versions through 0.2.4.
Likely exposure
Exposure is likely limited to WordPress sites that installed and enabled Availability Calendar versions 0.2.4 or earlier. The source bundle does not identify affected hosting platforms beyond WordPress plugin deployments.
Exploitation context
The provided data does not show CISA KEV listing or confirmed active exploitation. Practical exploitation requires user interaction, consistent with CSRF, and could result in stored script execution if the vulnerable workflow is reached.
Researcher notes
Evidence is sparse. The bundle confirms CSRF leading to stored XSS, CVSS 7.1, affected versions through 0.2.4, and no KEV flag. It does not provide a fixed version, proof-of-concept details, or confirmed exploitation.
Mitigation direction
- Inventory WordPress sites for Availability Calendar plugin slug availability.
- Disable or remove the plugin where business use is not confirmed.
- Check Patchstack, CVE, and vendor guidance for any fixed release or official workaround.
- Prioritize update or replacement when a maintained fixed version is available.
- Limit administrative exposure and require strong authentication while remediation is pending.
Validation and detection
- Confirm whether any WordPress site runs Availability Calendar version 0.2.4 or earlier.
- Check plugin inventory against the package name availability.
- Review site content and calendar changes for unauthorized stored script indicators.
- Track CVE and Patchstack records for fix or exploitation updates.
- Verify compensating controls do not replace vendor remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2025-46528 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.