dbcve.org
Customer Reassurance BlockPrestaShop extension · Prestashop

CVE-2023-47110

MEDIUM · 5.3 CVSS v3.1 Published 2023-11-09
Fix available
A fix is available. Upgrade to 5.1.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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
blockreassurance adds an information block aimed at offering helpful information to reassure customers that their store is trustworthy. An ajax function in module blockreassurance allows modifying any value in the configuration table. This vulnerability has been patched in version 5.1.4.

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 blockreassurance PrestaShop module contains an insecure ajax function that lacks proper authorization checks, allowing authenticated attackers to modify arbitrary configuration values in the database by manipulating the ajax endpoint.

MitigationUpdate the blockreassurance module to version 5.1.4 or later to apply the security patch. If immediate update is not possible, restrict access to the admin panel and disable the vulnerable ajax endpoint.

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
Customer Reassurance BlockPrestaShop extension
Affected:< 5.1.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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify blockreassurance module version
    Log into the PrestaShop admin panel, navigate to Modules > Module Manager, locate the 'Customer Reassurance Block' (blockreassurance) module, and note the installed version number.
    Affected if The installed version is lower than 5.1.4 (for example, 5.1.3, 5.1.0, or earlier)
  2. Check module file version as fallback
    If the admin panel is inaccessible, inspect the module directory. Navigate to /modules/blockreassurance/ and open the config.xml or composer.json file to read the version tag.
    Affected if The version found in the module files is lower than 5.1.4
  3. Confirm admin panel access status
    Check whether the PrestaShop admin directory (/admin or similar) is exposed to the public internet without IP restriction or VPN. Attempt to access the login page from an external network.
    Affected if The admin panel is publicly accessible without IP allowlisting or VPN tunneling
  4. Inspect the ajax endpoint existence
    Examine the module directory for the ajax controller file. Typical path is /modules/blockreassurance/controllers/admin/ajax.php or similar. Verify if this file handles configuration updates.
    Affected if The ajax.php file exists in the module's admin controller directory and accepts configuration parameter modifications without validation

You are affected if the blockreassurance module version is below 5.1.4 and the admin panel or ajax endpoint is accessible to authenticated users.

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

Update the blockreassurance module to version 5.1.4 or later to apply the security patch. If immediate update is not possible, restrict access to the admin panel and disable the vulnerable ajax endpoint.

Recommended fix High confidence

blockreassurance module version 5.1.4

  1. Backup your PrestaShop database and the current blockreassurance module files
  2. Navigate to the PrestaShop Addons marketplace or the module's official source and download version 5.1.4
  3. Log into the PrestaShop admin panel
  4. Go to Modules > Module Manager and uninstall the current blockreassurance module (or disable it)
  5. Upload and install the downloaded version 5.1.4
  6. Configure the module settings as needed
  7. Verify that the ajax function no longer allows unauthorized configuration changes

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

Fix this in Customer Reassurance Block Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47110 — 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-47110 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