dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-49896

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in wptasker WP Discord Post Plus – Supports Unlimited Channels allows Cross Site Request Forgery. This issue affects WP Discord Post Plus – Supports Unlimited Channels: from n/a through 1.0.2.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WP Discord Post Plus WordPress plugin allows attackers to induce authenticated administrators to perform unintended actions (such as sending Discord messages through the plugin) via maliciously crafted requests. The plugin lacks proper nonce validation on its administrative actions, enabling attackers to forge requests from a victim's browser when they are logged in.

MitigationImplement WordPress nonces on all form submissions and AJAX requests within the plugin, and verify the nonce validation on the server-side before processing any actions. Users should update to the latest patched version when available and limit admin access to trusted users.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Navigate to WordPress admin > Plugins and verify WP Discord Post Plus is installed and active, or run: wp plugin list --status=active --name='wp-discord-post-plus'
    Affected if The plugin is installed and active in WordPress
  2. Identify installed version
    In WordPress admin > Plugins, locate WP Discord Post Plus and note the version number displayed, or run: wp plugin get wp-discord-post-plus --format=json
    Affected if The installed version is unknown, older than the patched version, or cannot be determined
  3. Verify nonce validation exists
    Inspect the plugin's main PHP file (typically wp-discord-post-plus.php or similar) and locate admin action handlers. Search for wp_verify_nonce, check_admin_referer, or wp_nonce_field functions. Confirm these are present and called before processing any administrative actions
    Affected if No nonce verification functions are found in the plugin's admin action handlers, or nonce checks are missing entirely

If the WP Discord Post Plus plugin is installed and active but lacks proper nonce validation on its administrative action handlers, the environment is vulnerable to CVE-2025-49896 CSRF attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces on all form submissions and AJAX requests within the plugin, and verify the nonce validation on the server-side before processing any actions. Users should update to the latest patched version when available and limit admin access to trusted users.

Recommended fix Moderate confidence

Version 1.0.3 or later (check WordPress plugin repository for latest stable release)

  1. Check the WordPress admin dashboard under Plugins to confirm the current installed version of WP Discord Post Plus
  2. Navigate to Plugins > Add New > Upload Plugin or search for the plugin in the WordPress plugin repository
  3. If an updated version is available (typically 1.0.3 or higher), update the plugin through the WordPress admin interface
  4. After updating, verify the plugin is functioning correctly by testing Discord posting functionality
  5. Alternatively, navigate to Plugins > Add New and search for WP Discord Post Plus to check for the latest version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49896 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49896 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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