Deepen Video Conferencing with Zoom unauthorized data access in conferencing plugin
- Exploited
- No known exploitation
- Fix
- Fixed in 4.7.0
- Who is exposed
- Not reported
Summary
Video Conferencing with Zoom, a WordPress plugin by Deepen Bajracharya, has a broken access control flaw that lets an attacker gain high confidentiality impact. The attack can be launched remotely over the network without logging in.
Written by a model
Original description
Missing Authorization vulnerability in Deepen Bajracharya Video Conferencing with Zoom video-conferencing-with-zoom-api allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Video Conferencing with Zoom: from n/a through 4.6.12.
What to do
Upgrade to a fixed version: 4.7.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129013 (WordPress Video Conferencing with Zoom plugin <= 4.6.12 - Broken Access Control vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129013 (entry last updated 2026-11-19):
Affected:
- Deepen Bajracharya Video Conferencing with Zoom: fixed in 4.7.0
Fixed versions: 4.7.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129013 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129013 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/video-conferencing-with-zoom-api/vulnerability/wordpress-video-conferencing-with-zoom-plugin-4-6-12-broken-access-control-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-129013
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129013
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129013"}.Affected versions
- video-conferencing-with-zoom-apifixed in 4.7.0 · through 4.6.12
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129013 |
| Record | NVD · CVE-2026-129013 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/video-conferencing-with-zoom-api/vulnerability/wordpress-video-conferencing-with-zoom-plugin-4-6-12-broken-access-control-vulnerability?_s_id=cve |
Questions about CVE-2026-129013
Is CVE-2026-129013 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Users can reach pages or perform actions they should not be allowed to use, such as viewing other people's data. This is a broken access control flaw in the plugin.
Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-129013?
video-conferencing-with-zoom-api: through 4.6.12 (fixed in 4.7.0).
Source: cve.now feed data
Am I affected, and how do I check?
Versions of the Video Conferencing with Zoom WordPress plugin from the start up to and including 4.6.12 are in the affected range. Check the installed plugin version in the WordPress Plugins screen or the plugin's readme file.
Source: patchstack.com, cve.org
How do I fix CVE-2026-129013?
Update the Video Conferencing with Zoom plugin to version 4.7.0 or later, the fixed version named in the advisory.
Source: patchstack.com, cve.org
Related
- CVE-2026-66641WordPress Video Conferencing with Zoom plugin <= 4.6.8 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-103335WordPress Video Conferencing with Zoom plugin <= 4.6.10 - Sensitive Data Exposure vulnerability
- CVE-2024-33584WordPress Video Conferencing with Zoom plugin <= 4.4.4 - Open Redirection vulnerability
- CVE-2026-39653WordPress Video Conferencing with Zoom plugin <= 4.6.6 - Broken Access Control vulnerability
- CVE-2023-44142WordPress Inactive Logout plugin <= 3.2.2 - Broken Access Control vulnerability
- CVE-2026-131252Missing Authorization in Cross-Tenant Asset Management through the REST API in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.