dbcve.org
Socialfeed Photos \& Video Using Instagram ApiPrestaShop extension · Bontheme

CVE-2023-43982

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-03
Fix available
A fix is available. Upgrade to 7.0.0 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
Bon Presta boninstagramcarousel between v5.2.1 to v7.0.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the url parameter at insta_parser.php. This vulnerability allows attackers to use the vulnerable website as proxy to attack other websites or exfiltrate data via a HTTP call.

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 boninstagramcarousel module for PrestaShop contains a Server-Side Request Forgery (SSRF) vulnerability in the insta_parser.php file. The url parameter is not properly validated, allowing an attacker to control the server's HTTP requests. This enables the compromised server to be used as a proxy to attack external/internal systems or exfiltrate sensitive data.

MitigationImplement strict input validation and allowlisting for the url parameter in insta_parser.php. Consider disabling remote URL fetching entirely if not required, or restrict to approved domains only.

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
Socialfeed Photos \& Video Using Instagram ApiPrestaShop extension
Affected:>= 5.2.1, < 7.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
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. Confirm the boninstagramcarousel module is installed
    List installed PrestaShop modules via the admin panel or check the /modules/ directory for a folder named 'boninstagramcarousel' or similar Instagram-related module. Also search for 'Bontheme Socialfeed' or 'Socialfeed' in the modules list.
    Affected if The module folder exists in /modules/ and is listed in the PrestaShop admin under the name 'Socialfeed Photos & Video Using Instagram Api' or similar.
  2. Check the installed module version
    Open the main module file (usually boninstagramcarousel.php or config.xml in the module folder) and locate the version number. Compare it against the affected range: >= 5.2.1 and < 7.0.0.
    Affected if The version number is 5.2.1 or higher, but lower than 7.0.0.
  3. Locate the insta_parser.php file
    Search for the file insta_parser.php within the PrestaShop installation, typically under /modules/boninstagramcarousel/ or the module's main folder.
    Affected if The file insta_parser.php exists in the module directory.
  4. Verify the vulnerable url parameter handling
    Open insta_parser.php and search for code that handles a 'url' parameter in HTTP requests (look for $_GET['url'], $_POST['url'], or similar). Check if this url is used in file_get_contents, curl_exec, or similar functions without proper validation or allowlisting.
    Affected if The file contains code that accepts a 'url' parameter and uses it in server-side HTTP requests without strict validation.
  5. Check if remote URL fetching is enabled
    Review the module configuration in PrestaShop admin panel for settings related to Instagram API, remote content fetching, or URL imports. Check if there is an option to enable/disable remote URL retrieval.
    Affected if Remote URL fetching or Instagram content import features are enabled in the module settings.

You are affected if the Bontheme Socialfeed Instagram module (versions 5.2.1 through 6.x) is installed and the insta_parser.php file with the vulnerable url parameter exists and is 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 7.0.0 or later
Fixed in 7.0.0
Interim mitigation

Implement strict input validation and allowlisting for the url parameter in insta_parser.php. Consider disabling remote URL fetching entirely if not required, or restrict to approved domains only.

Recommended fix High confidence

7.0.0 or later

  1. Upgrade the Socialfeed Photos & Video Using Instagram Api module from any version >= 5.2.1 and < 7.0.0 to version 7.0.0 or later

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

Fix this in Socialfeed Photos \& Video Using Instagram Api 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-2023-43982 — 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-2023-43982 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