CVE-2026-7561
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Tm – WordPress Redirection plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Tm – WordPress Redirection plugin (versions up to 1.2) lacks proper nonce validation on a settings update function, allowing unauthenticated attackers to forge administrative requests. By tricking a site administrator into clicking a malicious link, attackers can modify plugin settings and inject malicious web scripts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedNavigate to WordPress admin > Plugins and check if 'Tm - WordPress Redirection' plugin appears in the installed plugins list. Alternatively, check if the directory wp-content/plugins/tm-redirection or similar exists on the server.Affected if The plugin is present in the plugins directory
-
Identify installed plugin versionOpen the main plugin file (typically in wp-content/plugins/tm-redirection/) and locate the version string in the plugin header comment, or check the Version field in the plugin admin UI.Affected if The version listed is 1.2 or lower (including any 1.x.x version below 1.2)
-
Locate the settings update functionInspect the plugin PHP files for any function that handles settings updates, typically named something like 'update_settings', 'save_settings', 'process_settings', or containing 'update_option' or 'register_settings'.Affected if A settings update function exists in the plugin code
-
Verify nonce validation is missingExamine the settings update function for nonce verification code. Look for presence of 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' calls within the function. If none are present, the vulnerability exists.Affected if The settings update function contains no nonce validation checks before processing changes
-
Confirm settings can be modified via forged requestIf logged in as administrator, attempt to access the plugin settings page and observe if the URL includes a nonce parameter. Then test if a request without a valid nonce parameter can be crafted to modify settings (do not actually modify settings, only verify the lack of protection).Affected if The plugin accepts and processes settings changes without requiring a valid nonce token
A user is affected if the Tm - WordPress Redirection plugin is installed with version 1.2 or lower and the settings update function lacks proper nonce validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAdd proper nonce validation to all state-changing functions in the plugin, particularly the settings update function. Update to version 1.3 or later when available.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7561 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7561 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data