CVE-2026-7616 MEDIUM

CVE-2026-7616: Zawgyi Embed <= 2.1.1 - Cross-Site Request Forgery via 'zawgyi_forceCSS' Parameter

Vendor Saturngod
Product Zawgyi Embed
Weakness CWE-352 · CSRF
Published May 12, 2026
Last update May 12, 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 Zawgyi Embed plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.1. This is due to missing or incorrect nonce validation on the zawgyi_adminpage function. This makes it possible for unauthenticated attackers to update the plugin's zawgyi_forceCSS setting by submitting a forged POST request to options-general.php?page=zawgyi_embed 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

Zawgyi Embed versions 2.1.1 and earlier are vulnerable to cross-site request forgery (CSRF). An attacker can craft a malicious webpage that, when visited by a logged-in user, performs unwanted actions on their behalf. The vulnerability requires user interaction—the victim must visit the attacker's page—and does not expose sensitive data, but can modify site content or settings.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on a user's account by tricking them into visiting a malicious webpage.

Potential impact on your site

04Site Impact

Users' accounts can be manipulated to perform unintended actions without their knowledge or consent.

Conditions required to exploit

05Prerequisites

Victim must be logged in and visit an attacker-controlled webpage; no special privileges required.

Key dates

06Disclosure timeline

May 12, 2026 CVE published
May 12, 2026 Record updated