CVE-2025-7650
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 · uneditedThe BizCalendar Web plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.1.0.53 via the 'bizcalv' shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
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 · high confidenceThe BizCalendar Web plugin for WordPress contains a Local File Inclusion (LFI) vulnerability in the 'bizcalv' shortcode affecting all versions up to 1.1.0.53. Authenticated attackers with Contributor-level access can include arbitrary server files and execute embedded PHP code, enabling privilege escalation, data exfiltration, and remote code execution.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify BizCalendar Web plugin is installedNavigate to WordPress admin > Plugins and locate BizCalendar Web in the list of installed plugins. Note the installed version number displayed.Affected if The plugin is installed and the version is 1.1.0.53 or lower.
-
Confirm Contributor-level or higher user accounts existCheck WordPress user management (Users > All Users) for accounts with Contributor, Author, Editor, or Administrator roles.Affected if At least one user account with Contributor-level access or higher exists on the site.
-
Identify published content using the bizcalv shortcodeSearch the WordPress database or content files for occurrences of the string 'bizcalv' in post_content, page_content, or custom post type content. Alternatively, use WordPress search with a plugin to list all shortcode usages.Affected if Any post, page, or custom post contains the [bizcalv] shortcode.
-
Inspect shortcode parameters for directory traversal patternsExamine the content containing [bizcalv] shortcode and review any parameters passed to it. Look for patterns like '../', '..\', absolute paths like '/etc/passwd' or 'C:\', or references to sensitive files.Affected if The shortcode includes parameters containing directory traversal sequences or references to system files outside the web root.
A user is affected if BizCalendar Web plugin version 1.1.0.53 or lower is installed, an authenticated user with Contributor-level access exists, and the bizcalv shortcode with suspicious parameters is present in any content.
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 dataUpdate BizCalendar Web plugin to version newer than 1.1.0.53 when available; temporarily disable the plugin if no update exists. Implement WAF rules to block directory traversal patterns in shortcode parameters as a defensive layer.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7650 — 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-7650 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