CVE-2026-1082
Unknown Unknown - Not Provided
CSRF Vulnerability in WordPress TITLE ANIMATOR Plugin Settings

Publication date: 2026-02-07

Last updated on: 2026-02-07

Assigner: Wordfence

Description
The TITLE ANIMATOR plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing nonce validation on the settings page form handler in `inc/settings-page.php`. This makes it possible for unauthenticated attackers to modify plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-07
Last Modified
2026-02-07
Generated
2026-06-16
AI Q&A
2026-02-07
EPSS Evaluated
2026-06-14
NVD
CVE-2026-1082
EUVD
EUVD-2026-5738
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
animator animator to 1.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The TITLE ANIMATOR plugin for WordPress has a Cross-Site Request Forgery (CSRF) vulnerability in all versions up to and including 1.0.

This vulnerability exists because the plugin's settings page form handler in the file inc/settings-page.php does not validate a security nonce.

As a result, an unauthenticated attacker can trick a site administrator into performing an action, such as clicking a malicious link, which then allows the attacker to modify the plugin's settings without authorization.

Impact Analysis

This vulnerability can allow an attacker to change the settings of the TITLE ANIMATOR plugin without permission.

Since the attacker must trick an administrator into clicking a link, the attack requires user interaction but does not require the attacker to be authenticated.

The impact is limited to integrity, meaning the attacker can alter plugin settings but cannot access confidential data or cause denial of service.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-1082. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart