Ap PagebuilderPrestaShop extension · Apollotheme

CVE-2024-6648

HIGH · 7.5 CVSS v3.1 Published 2025-05-08
Fix available
A fix is available. Upgrade to 4.0.0 or later.
See remediation →
84/100
Remediation priority · High
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
Absolute Path Traversal vulnerability in AP Page Builder versions prior to 4.0.0 could allow an unauthenticated remote user to modify the 'product_item_path' within the 'config' JSON file, allowing them to read any file on the system.

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

Absolute path traversal vulnerability in AP Page Builder versions prior to 4.0.0 allows unauthenticated remote attackers to modify the 'product_item_path' parameter in a config JSON file, enabling reading of arbitrary files on the system via the traversal attack.

MitigationUpgrade to AP Page Builder version 4.0.0 or later to obtain the vendor patch that addresses this vulnerability.

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
Ap PagebuilderPrestaShop extension
Affected:< 4.0.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 AP Page Builder installation
    Locate the AP Page Builder component in your CMS/website installation directory. Check for folders or modules named 'ap-pagebuilder', 'apollotheme', or similar.
    Affected if AP Page Builder component is present on the system
  2. Determine installed version
    Check the version file, composer.json, or module.xml within the AP Page Builder directory. Common locations include version.php, config.xml, or a dedicated version info file in the plugin/theme root.
    Affected if The installed version is lower than 4.0.0
  3. Locate config JSON file
    Search for JSON configuration files within the AP Page Builder directory that contain 'product_item_path' as a parameter. Check templates, configs, or settings folders.
    Affected if A config JSON file with the 'product_item_path' parameter exists and is writable or exposed via web request
  4. Verify web-accessible endpoint
    Test if the vulnerable parameter can be manipulated via HTTP request. Attempt to access a known file using path traversal (e.g., ../../) in the product_item_path parameter if an endpoint exists.
    Affected if The parameter accepts user input and allows path traversal sequences without sanitization

A user is affected if AP Page Builder version is below 4.0.0 AND the product_item_path parameter in the config JSON file is accessible or modifiable via web requests.

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 4.0.0 or later
Fixed in 4.0.0
Interim mitigation

Upgrade to AP Page Builder version 4.0.0 or later to obtain the vendor patch that addresses this vulnerability.

Recommended fix Moderate confidence

4.0.0

  1. Upgrade AP Page Builder to version 4.0.0 or later to resolve the path traversal vulnerability.
  2. After upgrading, verify that the 'product_item_path' parameter in the config JSON file cannot be manipulated to access arbitrary system files.
  3. Confirm the upgrade was successful by testing that file access is properly restricted.
Caveat Major version upgrades may introduce breaking changes; review release notes for 4.0.0 before deploying to production.

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

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

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-6648 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-6648 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