dbcve.org
Wp Plugin ManagerWordPress extension · Hasthemes

CVE-2025-64271

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-13
Fix available
A fix is available. Upgrade to 1.4.8 or later.
See remediation →
74/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 HasThemes WP Plugin Manager wp-plugin-manager allows Cross Site Request Forgery.This issue affects WP Plugin Manager: from n/a through <= 1.4.7.

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 HasThemes WP Plugin Manager allows attackers to trick authenticated administrators into performing unintended plugin management actions (install, activate, deactivate, remove) through maliciously crafted requests.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all state-changing plugin manager operations and validate these nonces server-side before executing any action.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Plugin ManagerWordPress extension
Affected:< 1.4.8

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
Low
Availability
None

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

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

  1. Locate the HasThemes WP Plugin Manager plugin
    In WordPress admin, go to Plugins > Installed Plugins and search for 'HasThemes WP Plugin Manager' or 'HasThemes'. Alternatively, check the /wp-content/plugins/ directory for a folder named similarly (e.g., ht-wp-plugin-manager, hasthemes-wp-plugin-manager, or similar).
    Affected if The plugin is installed and active on the WordPress site
  2. Identify the installed version number
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin to view its details, or check the main plugin file (usually named index.php or the plugin's main PHP file) for the 'Version' header in the plugin comment block. You can also check the readme.txt file in the plugin folder for the version number.
    Affected if The version number displayed is less than 1.4.8 (for example, 1.4.7, 1.4.6, 1.0, etc.)
  3. Confirm the plugin provides plugin management functionality
    Access the plugin settings or admin menu item (usually under 'Plugin Manager', 'HasThemes', or similar in the WordPress admin sidebar). Verify that the interface allows installing, activating, deactivating, or removing WordPress plugins.
    Affected if The plugin exposes any of these plugin management features (install, activate, deactivate, remove) in its admin interface

If the HasThemes WP Plugin Manager plugin is installed with a version lower than 1.4.8 and exposes plugin management features, the site is vulnerable to CSRF attacks that could manipulate plugins through tricked authenticated administrators.

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
Upgrade available Upgrade to 1.4.8 or later
Fixed in 1.4.8
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all state-changing plugin manager operations and validate these nonces server-side before executing any action.

Recommended fix High confidence

1.4.8

  1. Log into the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WP Plugin Manager' by HasThemes
  4. Click 'Update now' if an update is available, or manually download version 1.4.8 from the WordPress plugin repository and reinstall
  5. Verify the installed version is 1.4.8 or later

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

Fix this in Wp Plugin Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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