CVE-2024-2830 MEDIUM

CVE-2024-2830: WordPress Tag and Category Manager – AI Autotagger <= 3.13.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

Vendor Stevejburge
Product Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI
Weakness CWE-79 · XSS
Published April 4, 2024
Last update April 8, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The WordPress Tag and Category Manager – AI Autotagger plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'st_tag_cloud' shortcode in all versions up to, and including, 3.13.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Explanation of Vulnerability in Simple Terms

02Summary

The Tag, Category, and Taxonomy Manager plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in versions up to 3.12.0. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other site users, including administrators. The vulnerability affects the plugin's core functionality and can impact the entire site if an admin visits an affected page.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers, potentially stealing credentials or performing actions as those users.

Potential impact on your site

04Site Impact

Authenticated attackers can compromise admin accounts and site data through stored XSS. All site users viewing affected content are at risk.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress account (e.g., contributor or editor role). No user interaction required.

Key dates

06Disclosure timeline

April 4, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE