LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31572: WordPress Multi Days Events and Multi Events in One Day Calendar plugin <= 1.1.3 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in v20202020 Multi Days Events and Multi Events in One Day Calendar dragon-calendar-free-version allows Cross Site Request Forgery.This issue affects Multi Days Events and Multi Events in One Day Calendar: from n/a through <= 1.1.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31572 is a CSRF issue in a WordPress calendar plugin. A tricked logged-in site user could cause an unintended low-impact change. Sources rate it medium with CVSS 4.3, mainly because user interaction is required and no confidentiality or availability impact is listed.

Executive priority

Treat this as a moderate-priority WordPress plugin hygiene issue. It does not indicate data theft or service outage, but affected public sites should be reviewed because CSRF can enable unauthorized content or configuration changes through a logged-in user.

Technical view

The issue is CWE-352 in v20202020 Multi Days Events and Multi Events in One Day Calendar, package dragon-calendar-free-version, affecting versions through 1.1.3. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N indicates network reachability, low attack complexity, required user interaction, and low integrity impact.

Likely exposure

Exposure is limited to WordPress sites running the affected plugin at version 1.1.3 or earlier. Sites without this plugin, or using versions outside the cited affected range, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as KEV. The vulnerability type requires user interaction, consistent with a CSRF scenario where a legitimate user is induced to trigger an unintended action.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference. The public bundle identifies the vulnerability class, affected range, and CVSS vector, but does not provide endpoint details, proof of exploitation, or a named fixed version.

Mitigation direction

  • Inventory WordPress sites for the dragon-calendar-free-version plugin.
  • Update to a vendor-supported fixed version if one is available.
  • If no fix is available, disable or remove the plugin pending vendor guidance.
  • Limit privileged WordPress sessions to trusted devices and networks.
  • Tell administrators to avoid untrusted links while logged in.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record the installed plugin version and compare it to <= 1.1.3.
  • Review Patchstack, CVE, and vendor channels for current remediation guidance.
  • Check calendar or event records for unexpected recent changes.
  • Document any exposed site still running an affected version.
Prepared
Confidence
high
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-2025-31572 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
4.3 (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:N

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2025-31572Attack 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:N

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
v20202020Multi Days Events and Multi Events in One Day Calendardragon-calendar-free-version, 0unaffected
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.