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

CVE-2025-58846

HIGH · 7.1 CVSS v3.1 Published 2025-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 Dejan Markovic WordPress Buffer – HYPESocial. Social Media Auto Post, Social Media Auto Publish and Schedule buffer-my-post allows Reflected XSS.This issue affects WordPress Buffer – HYPESocial. Social Media Auto Post, Social Media Auto Publish and Schedule: from n/a through <= 2020.1.0.

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 WordPress HYPESocial (buffer-my-post) plugin enables attackers to trick authenticated administrators into performing unintended actions that result in reflected cross-site scripting (XSS). The lack of proper CSRF token validation on plugin actions allows malicious requests to be forged, which can then execute arbitrary JavaScript in the victim's browser.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing actions and forms, combined with proper input sanitization and output escaping to prevent the reflected XSS. Update the plugin to the latest patched version or remove it if unmaintained.

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
Low

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

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. Identify if HYPESocial plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'HYPESocial' or 'buffer-my-post' plugin. Alternatively, check the /wp-content/plugins/ directory for a folder named 'hypesocial' or 'buffer-my-post'.
    Affected if The plugin appears in the installed plugins list.
  2. Determine the installed plugin version
    In WordPress admin_plugins page, click 'View Details' on the HYPESocial/buffer-my-post plugin to see the version number. If using SSH, check the main plugin file header in /wp-content/plugins/[plugin-folder]/buffer-my-post.php for the 'Version' field.
    Affected if A version number is displayed and it is not the latest patched version.
  3. Verify admin access to plugin settings
    Navigate to the plugin settings page (usually under Settings > HYPESocial or a dedicated HYPESocial admin menu item) while logged in as an administrator.
    Affected if The plugin settings page loads and contains forms or action buttons that modify plugin configuration.
  4. Inspect plugin forms for CSRF protection tokens
    View the page source (right-click > View Page Source) of the plugin admin page. Search for 'nonce', '_wpnonce', or 'token' in the HTML forms. Check if each <form> tag contains an input field with name containing 'nonce' or '_wp'.
    Affected if Forms on the plugin admin page lack nonce fields or the nonce field value appears missing or invalid.
  5. Test for CSRF vulnerability via form action inspection
    Examine the HTML source of plugin forms to identify the 'action' parameter in the <form> tag and any <input> fields. Check if submitting these forms requires a valid nonce token by attempting to identify if the plugin verifies the nonce before processing the request (requires code review or dynamic testing).
    Affected if The plugin processes form submissions without verifying a CSRF token, allowing requests to be forged from other sites.

You are affected if the HYPESocial (buffer-my-post) plugin is installed and its admin forms do not implement proper CSRF nonce validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) on all state-changing actions and forms, combined with proper input sanitization and output escaping to prevent the reflected XSS. Update the plugin to the latest patched version or remove it if unmaintained.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58846 — 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-58846 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