dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1350

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-17
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
Missing Authorization vulnerability in Prasidhda Malla Honeypot for WP Comment.This issue affects Honeypot for WP Comment: from n/a through 2.2.3.

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

A Missing Authorization vulnerability exists in the Prasidhda Malla Honeypot for WP Comment plugin (versions up to 2.2.3). The vulnerability allows unauthenticated or unauthorized users to bypass the honeypot protection mechanism intended to block spam comments. This likely stems from missing capability checks or improper nonce validation in the plugin's comment processing functions.

MitigationUpdate the Honeypot for WP Comment plugin to the latest version which should include proper authorization checks. If no update is available, implement manual authorization checks (current_user_can() and nonce validation) in the plugin's comment handling functions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify plugin is installed
    Check for the presence of the Honeypot for WP Comment plugin in wp-content/plugins/ directory or via WordPress admin Plugins page
    Affected if Plugin is found in the WordPress installation
  2. Check installed version
    Read the plugin header comment in the main plugin file (typically honeypot-wp-comment.php) to obtain the Version field, or query via WP CLI: wp plugin get honeypot-wp-comment --field=version
    Affected if Version is 2.2.3 or lower
  3. Confirm plugin is active
    Check plugin status via WordPress admin or WP CLI: wp plugin is-active honeypot-wp-comment
    Affected if Plugin is active and processing comments
  4. Verify honeypot protection is configured
    Inspect plugin settings in WordPress admin under the Honeypot for WP Comment configuration page, or examine the wp_options table for relevant honeypot setting records
    Affected if Honeypot protection is enabled in plugin settings

User is affected if the plugin version is 2.2.3 or lower and the honeypot protection feature is active, since the missing authorization flaw allows bypassing this protection.

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

Update the Honeypot for WP Comment plugin to the latest version which should include proper authorization checks. If no update is available, implement manual authorization checks (current_user_can() and nonce validation) in the plugin's comment handling functions.

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

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 locally
dbcve dependency scanner

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