tagdiv vulnerabilities
Recent CVEs affecting tagdiv products. 7 tracked.
tagdiv has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 7. Most recent: 2025-05-08. Highest priority: CVE-2024-3813 (score 44/100).
- CVE-2025-3510 MEDIUM 6.4 UPGRADE The tagDiv Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple shortcodes
- CVE-2025-2806 MEDIUM 6.1 UPGRADE The tagDiv Composer plugin for WordPress, used by the Newspaper theme, is vulnerable to Reflected Cross-Site S
- CVE-2024-5212 MEDIUM 6.1 UPGRADE The tagDiv Composer plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘envato_code[
- CVE-2024-3886 MEDIUM 6.1 UPGRADE The tagDiv Composer plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘envato_code[
- CVE-2024-3815 MEDIUM 5.5 UPGRADE The Newspaper theme for WordPress is vulnerable to Stored Cross-Site Scripting via attachment meta in the arch
- CVE-2024-3814 MEDIUM 5.5 UPGRADE The tagDiv Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'single
- CVE-2024-3813 HIGH 8.8 UPGRADE The tagDiv Composer plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and incl
FAQ
How do I fix tagdiv vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is tagdiv being exploited right now?
None of the tracked tagdiv CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which tagdiv CVE should I patch first?
CVE-2024-3813 currently ranks highest (44/100): The tagDiv Composer plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and incl.