CVE-2025-1705: tagDiv Composer <= 5.3 - Cross-Site Request Forgery to Stored Cross-Site Scripting
First published: Fri Mar 28 2025(Updated: )
The tagDiv Composer plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.3. This is due to missing or incorrect nonce validation within the td_ajax_get_views AJAX action. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Credit: security@wordfence.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| KingComposer | <=5.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-1705?
CVE-2025-1705 has a medium severity rating due to its potential impact on user data and site security.
How do I fix CVE-2025-1705?
To fix CVE-2025-1705, update the tagDiv Composer plugin to version 5.4 or later that includes security patches.
Who is affected by CVE-2025-1705?
All versions of the tagDiv Composer plugin for WordPress up to and including 5.3 are affected by CVE-2025-1705.
What type of vulnerability is CVE-2025-1705?
CVE-2025-1705 is classified as a Cross-Site Request Forgery vulnerability.
Can CVE-2025-1705 be exploited by unauthenticated users?
Yes, CVE-2025-1705 can be exploited by unauthenticated attackers due to improper nonce validation.
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/references
- agent/weakness
- agent/title
- agent/type
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- agent/last-modified-date
- agent/severity
- agent/source
- agent/author
- agent/event
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/tagdiv
- canonical/kingcomposer