Pk CustomlinksApplication · Prestashop
CVE-2024-36684
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 · uneditedIn the module "Custom links" (pk_customlinks) <= 2.3 from Promokit.eu for PrestaShop, a guest can perform SQL injection. The script ajax.php have a sensitive SQL call that can be executed with a trivial http call and exploited to forge a SQL injection.
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 confidenceThe pk_customlinks module for PrestaShop versions 2.3 and below contains a SQL injection vulnerability in the ajax.php script. An unauthenticated guest can exploit this by sending specially crafted HTTP requests containing malicious SQL payloads that manipulate the backend SQL queries.
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
Pk CustomlinksApplication
<= 2.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the pk_customlinks module directoryCheck your PrestaShop modules folder (typically /modules/) for a directory named 'pk_customlinks'. If this directory exists, the module is installed.Affected if The pk_customlinks directory exists in the modules folder.
-
Identify the installed module versionOpen the main module file (often pk_customlinks.php or config.xml) inside the pk_customlinks directory and look for a version number. Compare this version against the affected range: <= 2.3Affected if The module version is 2.3 or lower.
-
Verify the vulnerable ajax.php script existsCheck for the presence of ajax.php within the pk_customlinks module directory (typically /modules/pk_customlinks/ajax.php).Affected if The ajax.php file exists in the pk_customlinks module directory.
-
Confirm module is enabledIn the PrestaShop admin panel, go to Modules > Module Manager and check whether pk_customlinks is installed and enabled. Alternatively, check the database table ps_module where name='pk_customlinks' and active=1.Affected if The module is installed and active in PrestaShop.
Your environment is affected if the pk_customlinks module version is 2.3 or lower and the ajax.php script is present and the module is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the pk_customlinks module to a version beyond 2.3 that contains the security patch. If an immediate update is unavailable, disable or remove the module. Consider deploying a WAF rule as a temporary mitigation.
pk_customlinks version > 2.3 (contact vendor for exact fixed release)
- Identify the current installed version of the pk_customlinks module in your PrestaShop installation
- Check Promokit.eu for the latest version of the pk_customlinks module (version higher than 2.3)
- Backup your PrestaShop database and files before performing any upgrade
- Upgrade the pk_customlinks module to the latest available version from Promokit.eu
- Verify the upgrade was successful and test the ajax.php functionality
- Confirm the SQL injection vulnerability is resolved by checking that ajax.php no longer accepts unsanitized SQL parameters
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pk Customlinks
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36684 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36684 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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