CVE-2025-28931
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in DevriX Hashtags wp-hashtags allows Stored XSS.This issue affects Hashtags: from n/a through <= 0.3.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 confidenceThe wp-hashtags plugin for WordPress contains a CSRF vulnerability that allows attackers to craft malicious requests which result in Stored XSS. The lack of proper anti-CSRF token validation on plugin actions enables attackers to inject malicious scripts that execute when administrators view affected content.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm wp-hashtags plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the wp-hashtags folderAffected if The plugin is present in the WordPress installation
-
Identify the installed versionIn Plugins list view, locate wp-hashtags and note the version number displayed under the plugin name; alternatively, read the main plugin file header in /wp-content/plugins/wp-hashtags/Affected if The installed version matches or falls within the known affected version range (compare against vulnerability disclosure sources)
-
Verify user input is accepted for hashtagsAccess the plugin settings page (typically under Settings or the plugin own menu) and determine if the plugin allows users to add, edit, or import hashtag content that gets stored in the databaseAffected if The plugin stores user-supplied hashtag content in the WordPress database
-
Inspect stored hashtag output for sanitizationView the source code of posts/pages where hashtags are displayed, or query the database table where hashtags are stored (check plugin documentation for table name) to see if raw user input is preserved without escapingAffected if Stored hashtag content is output to the page without proper sanitization or escaping functions (such as esc_html or esc_attr)
-
Check for CSRF token validation in plugin actionsExamine the plugin PHP source code for nonce verification on form submissions and AJAX actions; look for calls to wp_verify_nonce, check_admin_referer, or nonces in plugin formsAffected if Plugin forms and AJAX handlers lack nonce verification or do not validate CSRF tokens before processing user input
The environment is affected if the wp-hashtags plugin is installed, stores user-supplied hashtag content, and lacks proper CSRF token validation on actions that accept that input.
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 dataImplement WordPress nonces and proper CSRF token validation on all plugin actions that accept user input; sanitize and escape all user-supplied hashtag content before storage and output.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28931 — 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-2025-28931 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