CVE-2026-9722 MEDIUM

CVE-2026-9722: Laiser Tag <= 1.2.5 - Cross-Site Request Forgery to Plugin Settings Update via Settings Form

Vendor Pcis
Product Laiser Tag
Weakness CWE-352 · CSRF
Published June 2, 2026
Last update June 2, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Laiser Tag versions 1.2.5 and earlier are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without the administrator's knowledge or consent. The attacker has no special privileges and relies on the victim visiting a malicious link.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the site by tricking a logged-in admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

Administrators could unknowingly authorize changes to site settings or content if they visit a malicious link while logged in.

Conditions required to exploit

05Prerequisites

A site administrator must visit a malicious webpage while logged into the site.

Key dates

06Disclosure timeline

June 2, 2026 CVE published
June 2, 2026 Record updated

Related vulnerabilities

08Related CVE