dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-10578

HIGH · 8.8 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Pubnews theme for WordPress is vulnerable to unauthorized arbitrary plugin installation due to a missing capability check on the pubnews_importer_plugin_action_for_notice() function in all versions up to, and including, 1.0.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to install arbitrary plugins that can be leveraged to exploit other vulnerabilities.

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 Pubnews WordPress theme lacks proper capability validation in the pubnews_importer_plugin_action_for_notice() function, allowing any authenticated user with Subscriber-level permissions to trigger installation of arbitrary plugins. This broken access control vulnerability enables privilege escalation by installing plugins that can be weaponized for further attacks.

MitigationUpdate to version 1.0.8 or later which includes proper capability checks. If no patched version is available, remove the theme from production environments immediately.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Pubnews theme installation and version
    Locate the pubnews theme directory in wp-content/themes/ and read the version from style.css header or theme settings
    Affected if Theme is installed and version is lower than 1.0.8 or version cannot be determined
  2. Verify vulnerable function exists
    Search theme PHP files for the function name pubnews_importer_plugin_action_for_notice
    Affected if The function is found in the theme code, indicating the vulnerable code path is present
  3. Check for subscriber-level users
    Query WordPress user database (wp_users and wp_usermeta) or review user roles to identify accounts with Subscriber role
    Affected if Any authenticated users with Subscriber role exist in the WordPress installation
  4. Confirm importer functionality is accessible
    Review theme files to determine if the notice/import functionality that calls the vulnerable function is active and can be triggered by logged-in users
    Affected if The importer plugin notice feature is enabled and accessible to authenticated users regardless of role capability

A user is affected if the Pubnews theme is installed with a version below 1.0.8 and the vulnerable function is present, allowing any subscriber-level user to potentially install arbitrary plugins.

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 version 1.0.8 or later which includes proper capability checks. If no patched version is available, remove the theme from production environments immediately.

Recommended fix High confidence

1.0.8

  1. 1. Update the Pubnews theme to version 1.0.8 or later, which includes proper capability checks on the pubnews_importer_plugin_action_for_notice() function
  2. 2. Navigate to Dashboard > Appearance > Themes in the WordPress admin panel
  3. 3. If an update is available, click 'Update Now' on the Pubnews theme
  4. 4. Alternatively, download the latest version from wordpress.org/themes/pubnews/ and upload it via Dashboard > Appearance > Themes > Add New > Upload Theme
  5. 5. After updating, verify the fix by confirming that the pubnews_importer_plugin_action_for_notice() function now properly checks user capabilities before allowing plugin installation

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

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