The Remove NoFollow Commenter URL plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the gmz_comment_settings_save function. This makes it possible for unauthenticated attackers to modify the plugin's comment-display setting 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.
This CVE affects the WordPress Remove NoFollow Commenter URL plugin through version 1.0. A malicious site or link could trick a logged-in administrator into changing one plugin setting. The issue is limited to integrity impact in the cited sources, with no evidence of data theft, outage, or known active exploitation.
Executive priority
Treat as a moderate website hygiene issue. Prioritize affected public WordPress sites, especially where many administrators manage content. It is not presented as a breach-enabling flaw, but it can allow unauthorized configuration changes.
Technical view
The plugin’s gmz_comment_settings_save function lacks proper WordPress nonce validation, creating a CSRF condition. An unauthenticated attacker still needs administrator user interaction. The reported impact is modification of the plugin’s comment-display setting, rated CVSS 4.3 with low integrity impact only.
Likely exposure
Exposure is limited to WordPress sites running Remove NoFollow Commenter URL version 1.0 or earlier. Sites without this plugin are not affected by the cited issue.
Exploitation context
The source bundle does not show KEV listing or active exploitation. Exploitation requires social engineering a logged-in site administrator into taking an action that submits a forged settings update.
Researcher notes
The cited impact is narrow: CSRF to update a comment-display setting. Do not assume broader WordPress takeover, stored XSS, or data exposure without additional evidence. The affected-version metadata appears less clear than the narrative description, so verify against vendor records.
Mitigation direction
Inventory WordPress sites for Remove NoFollow Commenter URL version 1.0 or earlier.
Check vendor, WordPress plugin, and Wordfence guidance for a fixed release or official mitigation.
Disable or remove the plugin if no safe update is available and it is not essential.
Warn administrators against clicking untrusted links while authenticated to WordPress admin.
Validation and detection
Confirm whether the plugin is installed and record its version on each WordPress site.
Review the plugin settings for unexpected comment-display configuration changes.
Check whether gmz_comment_settings_save performs valid nonce verification in deployed code.
Review recent administrator sessions for suspicious setting changes or unusual referrers.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.