CVE-2025-28958
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Vadim Bogaiskov Bg Orthodox Calendar bg-orthodox-calendar allows Stored XSS.This issue affects Bg Orthodox Calendar: from n/a through <= 0.13.10.
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 confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in the Bg Orthodox Calendar plugin that enables Stored XSS attacks. An attacker can craft malicious requests that, when executed by an authenticated administrator or user, inject persistent malicious scripts into the calendar application that execute when other users view the affected content.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Bg Orthodox Calendar plugin is installedAccess your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Bg Orthodox Calendar' in the list of active plugins.Affected if The plugin appears in the list of installed plugins and is activated
-
Identify the installed versionIn the Plugins list, click on the plugin name or view details to read the version number displayed. Compare this version against the version range that includes the fix for CVE-2025-28958.Affected if The installed version is older than the patched version that addresses this CSRF-to-Stored-XSS flaw
-
Inspect admin state-changing operationsAccess the plugin settings or calendar management pages as an administrator. Use browser developer tools to examine forms for the presence of anti-CSRF tokens (such as hidden nonce fields) in POST requests that modify calendar data.Affected if Forms that add, edit, or delete calendar events lack CSRF tokens or nonce validation
-
Check for stored malicious scripts in calendar dataView the calendar on the frontend as a visitor. Use browser developer tools to inspect the page source and look for unsanitized script tags, iframe elements, or event handlers in calendar event titles, descriptions, or custom fields.Affected if User-supplied content in calendar events renders as executable HTML or JavaScript rather than being properly escaped
-
Review application logs for suspicious requestsExamine server access logs and WordPress audit logs for POST requests to admin-ajax.php or plugin admin pages that lack proper referer or token validation, especially if such requests originate from unexpected sources.Affected if Log analysis reveals state-changing requests without proper anti-CSRF validation headers
You are affected if the Bg Orthodox Calendar plugin is installed and its version is vulnerable to CVE-2025-28958, with forms lacking CSRF protection or stored XSS payloads present in calendar data.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF tokens for all state-changing operations and apply proper input validation and output encoding to prevent XSS injection and execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28958 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-28958 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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