The iTracker360 plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Stored Cross-Site Scripting in all versions up to and including 2.2.0. This is due to missing nonce verification on the settings form submission and insufficient input sanitization combined with missing output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via a forged request granted they can trick an administrator into performing an action such as clicking on a link.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
Required
User action required
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
References 7
https://plugins.trac.wordpress.org/browser/itracker360/tags/2.1.9/itracker360.p…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/itracker360/tags/2.1.9/itracker360.p…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/itracker360/tags/2.1.9/itracker360.p…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/itracker360/trunk/itracker360.php#L1…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/itracker360/trunk/itracker360.php#L1…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/itracker360/trunk/itracker360.php#L1…
security@wordfence.com
https://www.wordfence.com/threat-intel/vulnerabilities/id/5ef842ad-3d23-4206-af…
security@wordfence.com