dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-37477

MEDIUM · 6.5 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 →
71/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 Automattic Newspack Content Converter allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Newspack Content Converter: from n/a through 0.1.5.

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

The Newspack Content Converter plugin for WordPress contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. Users without proper permissions can potentially access or manipulate conversion functionality that should be restricted to authorized users only.

MitigationImplement proper authorization checks on all sensitive plugin endpoints and verify access control configurations are correctly set to enforce role-based permissions.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Confirm Newspack Content Converter is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Newspack Content Converter' in the installed plugins list. Note whether it is activated or deactivated.
    Affected if The plugin is installed and activated in WordPress.
  2. Identify the installed plugin version
    In the Plugins page, click on the plugin name to view its details, or inspect the plugin header comment in the main PHP file (typically at wp-content/plugins/newspack-content-converter/newspack-content-converter.php) to find the Version field.
    Affected if The installed version falls within the vulnerable version range for this CVE.
  3. Verify WordPress user roles with conversion access
    Go to Users > All Users in the WordPress admin. Review which users have roles that would typically have access to plugin settings or conversion functionality (Administrator, Editor, or custom roles).
    Affected if User accounts exist with roles that should not have access to conversion features.
  4. Test conversion endpoint access with limited user
    Create or use a limited-privilege user account (such as Subscriber or Contributor). Attempt to access the plugin conversion URL or function directly (commonly at /wp-admin/admin.php?page=newspack-content-converter or via REST API endpoint /wp-json/newspack-content-converter/v1/convert).
    Affected if A user without Administrator or appropriate privileges can access or trigger conversion operations.
  5. Inspect plugin capability checks
    Access the plugin files via FTP or File Manager. Review the main plugin PHP files for function calls that check user capabilities (functions like current_user_can, wp_get_current_user, or permission callbacks). Look for endpoints or AJAX actions lacking these checks.
    Affected if Conversion-related functions or endpoints lack proper current_user_can() or capability validation checks.

A user is affected if the Newspack Content Converter plugin is active, lacks proper authorization checks on its conversion endpoints, or allows non-privileged users to access conversion functionality.

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

Implement proper authorization checks on all sensitive plugin endpoints and verify access control configurations are correctly set to enforce role-based permissions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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