Laiser Tag <= 1.2.5 - Cross-Site Request Forgery to Plugin Settings Update via Settings Form
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.3epss 0.1%
exploitation probability
0.1%top 97% of all CVEs
observed exploitation
nono source reports it
The Laiser Tag plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.5. This is due to missing or incorrect nonce validation on the addOptionsPageFields function. This makes it possible for unauthenticated attackers to update the plugin's settings, including the API key, tag blacklist, relevance threshold, batch size, and tagging toggles, via a forged request via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Affected products
pcis · Laiser TagReferences
https://plugins.trac.wordpress.org/browser/laiser-tag/trunk/include/Tagging.php#L200https://plugins.trac.wordpress.org/browser/laiser-tag/trunk/include/Tagging.php#L212https://plugins.trac.wordpress.org/browser/laiser-tag/trunk/templates/adminOptionPage.php#L91https://www.wordfence.com/threat-intel/vulnerabilities/id/ed3aaa2a-8211-409c-8a75-1ac59e1d55e2?source=cve