dbcve.org
Ht FeedWordPress extension · Hasthemes

CVE-2023-23804

HIGH · 8.8 CVSS v3.1 Published 2023-07-10
Fix available
A fix is available. Upgrade to 1.2.8 or later.
See remediation →
95/100
Remediation priority · Urgent
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 HasThemes HT Feed plugin <= 1.2.7 versions.

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 HasThemes HT Feed WordPress plugin versions 1.2.7 and below. The flaw allows attackers to trick authenticated administrators into performing unintended actions by forging malicious requests, potentially leading to unauthorized configuration changes or data manipulation within the plugin.

MitigationUpdate HT Feed plugin to the latest patched version once released. Until then, implement anti-CSRF tokens (nonces) on all form submissions and AJAX actions within the plugin to prevent forged requests.

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
Ht FeedWordPress extension
Affected:< 1.2.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check HT Feed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins. Locate 'Hasthemes HT Feed' and read the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' comment.
    Affected if The version number is 1.2.7 or lower, or if no version is displayed but the plugin is known to be from before version 1.2.8
  2. Verify plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm that 'Hasthemes HT Feed' shows as 'Active' under the plugin status.
    Affected if The plugin is active and the version is below 1.2.8; inactive plugins still have the vulnerability in their code but are not exploitable in the current state
  3. Inspect form submissions for nonce protection
    Access the plugin directory via FTP or file manager (wp-content/plugins/ht-feed/). Open PHP files and search for form tags (form method="post"). Check if each form includes a nonce field such as wp_nonce_field(), nonce_field(), or a hidden input with a name containing '_nonce' or 'token'.
    Affected if Form submissions lack nonce verification code, meaning CSRF tokens are not being generated or validated on those forms
  4. Inspect AJAX actions for nonce verification
    Search the plugin PHP files for 'add_action' calls registering AJAX handlers (wp_ajax_). For each handler found, verify there is a corresponding 'check_ajax_referer' or 'wp_verify_nonce' call before processing the request.
    Affected if AJAX actions do not verify nonces before executing, allowing attackers to forge requests on behalf of authenticated admins

You are affected if the HT Feed plugin is active and the installed version is below 1.2.8 AND the plugin lacks nonce verification on its forms or AJAX handlers.

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.2.8 or later
Fixed in 1.2.8
Interim mitigation

Update HT Feed plugin to the latest patched version once released. Until then, implement anti-CSRF tokens (nonces) on all form submissions and AJAX actions within the plugin to prevent forged requests.

Recommended fix High confidence

1.2.8

  1. Backup the WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the HT Feed plugin in the list of installed plugins
  4. Click Update Now on the HT Feed plugin, or manually upload version 1.2.8 or later
  5. Verify the update completed successfully by checking the installed plugin version
  6. Test the plugin functionality to ensure it operates correctly after the update

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

Fix this in Ht Feed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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