Wpvnteam develops WordPress-focused plugins and extensions, with observed vulnerabilities centered on the WP Extra product and recurring around authorization gaps, cross-site request forgery, and code-injection issues typical of WordPress plugin development. These weakness classes reflect the plugin architecture's exposure to user-controlled input and the integration points between plugin code and WordPress core. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Wpvnteam over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-46623HIGH Improper Control of Generation of Code ('Code Injection') vulnerability in TienCOP WP EXtra.This issue affects WP EXtra: from n/a through 6.2. | Dec 29, 2023 | 8.8 | 26 | NO | NO |
CVE-2023-46212HIGH Missing Authorization, Cross-Site Request Forgery (CSRF) vulnerability in TienCOP WP EXtra allows Accessing Functionality Not Properly Constrained by ACLs, Cross Site Request Forge | Dec 19, 2023 | 8.8 | 24 | NO | NO |
CVE-2023-47825HIGH Cross-Site Request Forgery (CSRF) vulnerability in TienCOP WP EXtra plugin <= 6.4 versions. | Nov 22, 2023 | 8.8 | 24 | NO | NO |
CVE-2023-5311HIGH The WP EXtra plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the register() function in versions up to, and including, | Oct 25, 2023 | 8.8 | 24 | NO | NO |
CVE-2023-5314MEDIUM The WP EXtra plugin for WordPress is vulnerable to unauthorized access to restricted functionality due to a missing capability check on the 'test-email' section of the register() f | Nov 22, 2023 | 4.3 | 16 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Wpvnteam.
Media articles that mention a CVE ID that affects a product developed by Wpvnteam — matched by CVE ID, not by vendor name.