dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-7621

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-12
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
The Visual Website Collaboration, Feedback & Project Management – Atarim plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the process_wpfeedback_misc_options() function in all versions up to, and including, 4.0.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update the plugins settings which can also be leveraged to gain access to the plugin's settings.

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 · high confidence

The Atarim WordPress plugin versions up to 4.0.2 lack a capability check on the process_wpfeedback_misc_options() function, allowing any authenticated user with Subscriber-level access or higher to modify plugin settings via an insecure direct object reference.

MitigationUpdate the Atarim plugin to version 4.0.3 or later which includes the missing capability check. If an update is unavailable, add a capability verification (e.g., current_user_can('manage_options')) to the process_wpfeedback_misc_options() function.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Atarim plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Atarim' or 'WPFeedback' plugin in the list
    Affected if The Atarim plugin appears in the installed plugins list
  2. Check installed plugin version
    In the Plugins list, look at the version number displayed below the plugin name, or check the plugin's main PHP file (usually atarim.php or wpfeedback.php) for the 'Version' header in the file comment
    Affected if Version is 4.0.2 or lower (or no version is displayed indicating an old install)
  3. Verify authenticated user access exists
    Go to WordPress admin > Users and check if any users exist with the Subscriber role (or any role other than Administrator)
    Affected if At least one user with Subscriber-level or higher access exists on the site
  4. Inspect the vulnerable function for capability check
    Locate the plugin file containing process_wpfeedback_misc_options() function and search for 'current_user_can' within that function to verify a capability check exists
    Affected if The function exists but contains no current_user_can() call, or only checks for a low-privilege capability like 'edit_posts' instead of 'manage_options'

The environment is affected if the Atarim plugin version is 4.0.2 or lower AND any authenticated user with Subscriber-level access or higher exists AND the process_wpfeedback_misc_options() function lacks a proper capability check like current_user_can('manage_options').

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 the Atarim plugin to version 4.0.3 or later which includes the missing capability check. If an update is unavailable, add a capability verification (e.g., current_user_can('manage_options')) to the process_wpfeedback_misc_options() function.

Recommended fix High confidence

Atarim plugin version 4.0.3 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Visual Website Collaboration, Feedback & Project Management – Atarim'
  4. Click 'Update Now' if an update is available, or manually download version 4.0.3 or later from WordPress.org and upload via Plugins > Add New > Upload Plugin
  5. Verify the plugin updated successfully by checking the version number

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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