dbcve.org
PbootcmsApplication

CVE-2024-12789

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-19
Fix available
A fix is available. Upgrade to 3.2.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A vulnerability was found in PbootCMS up to 3.2.3. It has been classified as critical. This affects an unknown part of the file apps/home/controller/IndexController.php. The manipulation of the argument tag leads to code injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 3.2.4 is able to address this issue. It is recommended to upgrade the affected component.

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

A code injection vulnerability exists in PbootCMS up to version 3.2.3 in the IndexController.php file where the 'tag' parameter is not properly sanitized, allowing remote attackers to inject and execute arbitrary code. This unauthenticated vulnerability has a public exploit and a CVSS score of 9.8 indicates trivial exploitability with complete system compromise potential.

MitigationUpgrade PbootCMS to version 3.2.4 immediately to remediate this vulnerability. If immediate upgrade is not possible, consider disabling the affected endpoint or implementing WAF rules as a temporary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PbootcmsApplication
Affected:< 3.2.4

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

CVSS:3.1/AV:N/AC:L/PR:N/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 PbootCMS installation and version
    Check the version.php or common version files in the PbootCMS installation directory, or look for a version indicator in the admin panel under System > System Information
    Affected if The installed version is lower than 3.2.4 (any version from 3.2.3 and below)
  2. Locate the vulnerable IndexController.php file
    Find the IndexController.php file in the controller directory of the PbootCMS installation (typically in /app/index/controller/ or similar path)
    Affected if The file exists in the installation, indicating the vulnerable component is present
  3. Inspect the 'tag' parameter handling in IndexController.php
    Open IndexController.php and search for the 'tag' parameter handling code, specifically looking for where user input is used without proper sanitization
    Affected if The code shows the 'tag' parameter is processed without sanitization or validation (look for direct use of input in queries or eval-like functions)
  4. Determine if the tag feature is accessible
    Check if the tag functionality is enabled in the CMS configuration and accessible via the frontend (typically at URLs like /?tag= or /search/?tag=)
    Affected if The tag feature is enabled and publicly accessible without authentication

You are affected if PbootCMS version is below 3.2.4 AND the vulnerable IndexController.php file contains the unsanitized 'tag' parameter handling AND the tag feature is enabled and accessible.

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
Upgrade available Upgrade to 3.2.4 or later
Fixed in 3.2.4
Interim mitigation

Upgrade PbootCMS to version 3.2.4 immediately to remediate this vulnerability. If immediate upgrade is not possible, consider disabling the affected endpoint or implementing WAF rules as a temporary measure.

Recommended fix High confidence

PbootCMS 3.2.4

  1. 1. Create a complete backup of the current PbootCMS installation including all files and the database
  2. 2. Download PbootCMS version 3.2.4 from the official repository (github.com/pbootcms/PbootCMS) or the official website
  3. 3. Extract the downloaded package
  4. 4. Replace the existing files with the new version 3.2.4 files, preserving the /static and /config directories if prompted
  5. 5. Verify the application functions correctly after the upgrade
  6. 6. Test that the previously vulnerable endpoint (apps/home/controller/IndexController.php with the 'tag' parameter) no longer accepts injection attempts
Caveat Review release notes for any breaking changes between your current version and 3.2.4; test in staging before production deployment

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

Fix this in Pbootcms 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 the upgrade done

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