dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-43273

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 icegram Icegram Collect plugin allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Icegram Collect plugin: from n/a through 1.3.14.

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

Missing authorization vulnerability in the Icegram Collect WordPress plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to sensitive data or functionality due to improper permission checks.

MitigationUpdate to the latest version of Icegram Collect when a patched release becomes available, or add proper capability checks and nonce verification to all AJAX handlers and admin pages.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Locate Icegram Collect plugin installation
    Check for the plugin directory at wp-content/plugins/icegram-collect/ or search for 'icegram' in the WordPress plugins folder
    Affected if The plugin directory icegram-collect does not exist in the plugins folder, meaning the plugin is not installed
  2. Identify the installed version
    Open the main plugin file (usually icegram-collect.php) and look for the version header comment, typically found in the plugin file header under 'Version: x.x.x'
    Affected if The installed version is lower than the patched version (if known) or cannot be determined to be the latest secure release
  3. Inspect AJAX handlers for missing capability checks
    Search the plugin files for add_action calls registering AJAX actions (wp_ajax_ or wp_ajax_nopriv_) and verify each handler calls current_user_can() or a similar capability check function before executing sensitive operations
    Affected if Any AJAX handler processes requests without first verifying user capabilities or permissions
  4. Verify nonce verification on AJAX actions
    Search AJAX handler functions for nonce verification calls such as check_ajax_referer() or wp_verify_nonce() before processing the request
    Affected if AJAX handlers process requests without validating nonces, allowing potential CSRF attacks
  5. Check admin pages for authorization checks
    Examine any admin menu registration (add_menu_page, add_submenu_page) and the corresponding callback functions to ensure they call current_user_can() or proper permission checks before displaying sensitive data
    Affected if Admin pages render content or functionality without verifying the current user has appropriate capabilities

The environment is affected if Icegram Collect plugin is installed and any AJAX handler or admin page lacks proper capability checks and nonce verification before executing sensitive operations or exposing data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Icegram Collect when a patched release becomes available, or add proper capability checks and nonce verification to all AJAX handlers and admin pages.

Recommended fix Moderate confidence

1.3.15 or later (check WordPress plugin repository for latest fixed release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Icegram Collect plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version that includes the authorization fix
  5. 5. After updating, verify the plugin is functioning correctly on the site
  6. 6. Review user role capabilities and access controls within the plugin settings to ensure proper authorization is enforced

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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