New View larger

Prestashop audit sources

Read-only audit of a PrestaShop store: files only – €190 excl. tax; files, database, and logs – from €390 excl. tax. The report serves as the basis for a cleanup service (offered separately, starting at €490 excl. tax); the cost of the audit will be deducted if the cleanup service is ordered within 30 days.

More details

228,00 € tax incl.

* required fields

More info

Purpose of this audit

When taking over an online store, migrating a server, or if there is any doubt regarding a site's integrity, the source files and database may contain PHP files placed outside the PrestaShop core, content injected into text fields, or user accounts and modules that do not belong to the project.

The audit is performed in read-only mode. Nothing is modified, deleted, cleaned, or shared with any third party. The report identifies the relevant files and database records, their apparent dates, and access details—which can be cross-referenced with server logs, provided those logs are still available.

Following the report, the sources and databases are deleted from the local copy, unless the client wishes for the cleanup to be performed by AI-DEV.

Scope

  • public_html directory structure: core files, modules, themes, overrides, images, uploads, and directories that are typically empty.
  • Version consistency: AppKernel, config, classes, and dependencies, to detect any interrupted updates.
  • Database: editable text content (products, categories, CMS pages, configuration), store URLs, employee accounts, and a comparison between registered modules and the directories actually present on the disk.
  • Web server, PHP, and PrestaShop logs (if they have not been lost during a migration).

What the report identifies

  • Files that are not part of the PrestaShop core or any identifiable module, including their location and file timestamp (note that this timestamp may have been altered).
  • Orphaned directories: those present on the disk but missing from the modules table, or vice versa.
  • Active employee accounts, their assigned profiles, and the date their passwords were last changed.

Password hashes are not included in the report.

  • The results of searches within the database text: either injected code is visible, or no matches were found in the columns examined.
  • URLs, keys, and messaging or payment settings that need to be renewed—without copying their actual values.
  • Information that can be dated based on logs, or the fact that such logs are missing, making it impossible to reconstruct actual file access.

Pricing

Amounts are exclusive of tax. For companies based in France, a 20% VAT will be added.

ServicePriceScenario
Audit €190 excl. tax Audit of source code only
Audit €390 excl. tax Full audit for a small organization (annual turnover under €200k)
Audit €690 excl. tax Full audit for a large organization (annual turnover over €200k)
Cleanup €490 excl. tax Specific files identified, core system intact, access credentials renewed, follow-up verification
Cleanup €990 excl. tax Multiple repositories, core system verification, keys and accounts renewed, secondary verification check
Cleanup from €1,490 excl. tax Compromised core system: reinstallation based on pre-filtered/cleaned data

The cost for cleanup is determined within the audit report itself, not beforehand. If cleanup services are ordered within 30 days of the report's delivery, the cost of the audit will be deducted from the cleanup fee.

What is not included in the audit

  • File deletion, core restoration, or password rotation. These actions are handled as a separate service, following approval of the audit report.
  • Analysis of a server where logs have been erased prior to the copy: the report will note this, but will not attempt to reconstruct them.
  • Penetration testing of the server, network, or administrative workstations.

Process (depending on the chosen option)

  1. Creation of a working copy of the source files and a database export. The live (production) store remains unchanged.
  2. Searching through the files, followed by a search within the text columns of the database.
  3. Reviewing available logs and cross-referencing them with the files identified.
  4. Delivery of the report: findings, limitations, and a list of secrets (credentials/keys) that need to be renewed.

Information to provide

  • Access to the hosting provider's console, if you would like AI-DEV to handle everything

or

  • Source code archive or read access to the directory.
  • Database export, or read-only access. Employee and client passwords may be removed from the export before it is sent.
  • Web server access and error logs, PHP logs, and the contents of var/logs, covering the longest possible time period.

Estimated audit duration

1 to 2 days, depending on the selected package and the size of the site.

Avis