dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2024-38775

HIGH · 7.2 CVSS v3.1 Published 2024-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Improper Privilege Management vulnerability in WebAppick CTX Feed allows Privilege Escalation.This issue affects CTX Feed: from n/a through 6.5.6.

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

Improper Privilege Management vulnerability in WebAppick CTX Feed plugin for WordPress allows authenticated users with low-level privileges (likely Subscriber or Contributor roles) to perform actions that should require higher privileges, enabling privilege escalation. The plugin fails to properly validate user capabilities before executing privileged operations.

MitigationUpdate CTX Feed to the latest patched version once released. Until then, restrict user registration and carefully audit user roles assigned to the site, removing any untrusted low-privilege accounts that shouldn't have access.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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. Verify CTX Feed plugin is installed
    Navigate to WordPress admin > Plugins and look for 'CTX Feed' or 'WebAppick CTX Feed' in the installed plugins list. Note whether it is activated.
    Affected if The plugin is installed and activated on the WordPress site.
  2. Determine installed CTX Feed version
    In Plugins list, click on the CTX Feed plugin to view its details, or check the plugin files in /wp-content/plugins/ for a version indicator in the main PHP file or readme.txt.
    Affected if The installed version is older than the latest patched version released to address CVE-2024-38775.
  3. Check if user registration is enabled
    Go to WordPress admin > Settings > General and look for the 'Membership' setting, or inspect the site's wp-options table for the 'users_can_register' setting set to 1.
    Affected if User registration is enabled, allowing potential attackers to create low-privilege accounts.
  4. Identify low-privilege user accounts
    Go to WordPress admin > Users and review accounts with Subscriber or Contributor roles. Check for any unexpected or untrusted accounts at these levels.
    Affected if There are untrusted or unexpected user accounts assigned Subscriber or Contributor roles.

A user is affected if CTX Feed plugin is installed with a vulnerable version and the site has low-privilege user accounts (Subscriber/Contributor) present, particularly with registration enabled.

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 CTX Feed to the latest patched version once released. Until then, restrict user registration and carefully audit user roles assigned to the site, removing any untrusted low-privilege accounts that shouldn't have access.

Recommended fix Moderate confidence

CTX Feed version 6.5.7 or later (latest available version)

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Locate the CTX Feed plugin by WebAppick
  5. 5. Check the current version - if it is 6.5.6 or lower, an update is needed
  6. 6. If an update is available, click 'Update Now' to upgrade to the latest version
  7. 7. Verify the plugin updated successfully and test that the CTX Feed functionality works correctly
  8. 8. Confirm the privilege escalation vulnerability is resolved by testing that lower-privileged users cannot access administrative functions they should not have
Caveat Review plugin changelog for any breaking changes between your current version and the new version before updating in production

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-38775 — 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-38775 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