CVE-2025-5936: The VR Calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and in

Q: How do I fix CVE-2025-5936?

vr calendar: upgrade to newer than 2.4.7. Exact commands for each OS are on this page.

Q: Is CVE-2025-5936 being exploited?

CVE-2025-5936 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-5936 affect?

CVE-2025-5936 affects vr calendar. Severity is medium (CVSS 4.3). The VR Calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.4.7. This is due to missing or incorrect nonce validation on the syncCalendar() function. This makes it possible for un

Q: How urgent is CVE-2025-5936?

Priority 16/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2025-5936 is a medium-severity flaw (CVSS 4.3) affecting vr calendar. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The VR Calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.4.7. This is due to missing or incorrect nonce validation on the syncCalendar() function. This makes it possible for unauthenticated attackers to trigger a calendar sync via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.1% (top 97%)
CISA exploited list	No
Weakness	CWE-352
Published	2025-06-27
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: vr calendar project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-06-27 08:15 UTCPublished CVE record published
2026-06-17 09:49 UTCUpdated Record last modified

vr calendar project vr calendar UPGRADE

Affected: <= 2.4.7

Fixed in: newer than 2.4.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vr-calendar || rpm -q vr-calendar || vr-calendar --version

2. UPGRADE to newer than 2.4.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vr-calendar

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vr-calendar

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-5936?

vr calendar: upgrade to newer than 2.4.7. Exact commands for each OS are on this page.

Is CVE-2025-5936 being exploited?

CVE-2025-5936 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-5936 affect?

CVE-2025-5936 affects vr calendar. Severity is medium (CVSS 4.3). The VR Calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.4.7. This is due to missing or incorrect nonce validation on the syncCalendar() function. This makes it possible for un

How urgent is CVE-2025-5936?

Priority 16/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs