Vulnerability Details CVE-2013-3526
Cross-site scripting (XSS) vulnerability in js/ta_loaded.js.php in the Traffic Analyzer plugin, possibly 3.3.2 and earlier, for WordPress allows remote attackers to inject arbitrary web script or HTML via the aoid parameter.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.082
EPSS Ranking 91.8%
CVSS Severity
CVSS v2 Score 4.3
References
- http://osvdb.org/92197
- http://packetstormsecurity.com/files/121167/WordPress-Traffic-Analyzer-Cross-Site-Scripting.html
- http://secunia.com/advisories/52929
- http://www.securityfocus.com/bid/58948
- https://exchange.xforce.ibmcloud.com/vulnerabilities/83311
- http://osvdb.org/92197
- http://packetstormsecurity.com/files/121167/WordPress-Traffic-Analyzer-Cross-Site-Scripting.html
- http://secunia.com/advisories/52929
- http://www.securityfocus.com/bid/58948
- https://exchange.xforce.ibmcloud.com/vulnerabilities/83311
Products affected by CVE-2013-3526
-
cpe:2.3:a:wordpress:wordpress:-
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.0.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.1.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.1.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.1.2
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.1.3
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.2.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.3.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.4.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.5.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.6.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.6.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.7.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.8.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:1.9.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.0.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.1.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.2.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.2.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.3.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.4.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.4.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.5.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.5.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.5.2
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.6.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.7.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.7.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.8.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.8.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.8.2
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.9.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:2.9.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.0.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.0.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.0.2
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.0.3
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.1.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.2.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.2.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.3.0
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.3.1
-
cpe:2.3:a:wptrafficanalyzer:trafficanalyzer:3.3.2