← WordPress Vulnerabilities
WordPress security by component

Responsive Plus

Responsive Plus is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Jun 17, 2025; the highest CVE/CNA score is 6.4.

Plugin slug: responsive-add-ons

CVE-2025-49856: Responsive Plus: Cross-site request forgery

Responsive Plus is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

PublishedJun 17, 2025
Safe version guidanceSee mitigation notes
Safe version
Jun 17, 2025 CVE-2025-49856
Responsive Plus: Cross-site request forgery
Responsive Plus is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
See mitigation notes
CVE4.3
NVDPending
Jun 06, 2025 CVE-2025-48335
Responsive Plus: A security weakness
Responsive Plus is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.4
NVDPending
May 07, 2025 CVE-2025-47486
Responsive Plus: A security weakness
Responsive Plus is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.3
NVDPending
Jun 05, 2024 CVE-2024-5222
Responsive Addons – Starter Templates, Advanced Features and Customizer Settings for Responsive Theme: Cross-site scripting
Responsive Addons – Starter Templates, Advanced Features and Customizer Settings for Responsive Theme is affected by cross-site scripting. Exploitation requires at least author-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVD5.4