WordPress security by component
Disqus Comment System
Plugin description
Disqus Comment System is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Aug 19, 2014; the highest published CVSS base score is 6.8.
Plugin slug:
disqus-comment-systemLatest vulnerability
CVE-2014-5347: Disqus Comment System: Cross-site scripting
Disqus Comment System is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| Aug 19, 2014 |
CVE-2014-5347
Disqus Comment System: Cross-site scripting
Disqus Comment System is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVEPending
NVD6.8
|
| Aug 19, 2014 |
CVE-2014-5346
Disqus Comment System: Cross-site request forgery
Disqus Comment System 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. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVEPending
NVD6.8
|
| Aug 19, 2014 |
CVE-2014-5345
Disqus Comment System: Cross-site scripting
Disqus Comment System is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVEPending
NVD4.3
|