Security Guide for modified eCommerce Shop Operators: Step-by-Step Instructions & Basic Rules

Security Update – November 18, 2026: Another Security Package Announced
New information from November 18, 2026, at 7:00 PM: The modified development team has announced another security package. Additional security fixes are therefore being prepared and will also be relevant for stores that have already been updated.
Particularly important: Even if you have already installed the security fixes released on November 13, 2026, you will still need to take the new security package into account once it becomes available.
Do not wait for the new security package!
The security fixes already available should still be installed immediately. The upcoming package will supplement the existing measures, but it does not remove the need to address known security vulnerabilities now.
How to Prepare for the Upcoming Update
- Schedule the update: Reserve sufficient time for installation or arrange an appointment with your technical service provider.
- Create a complete backup: Back up all shop files and the database before updating.
- Check your shop version: Identify your installed modified version to ensure the correct security fixes are applied.
- Review customizations: Individually modified core files and previously installed module updates must be carefully compared before files are overwritten.
Existing stores: Once the new security package becomes available, it must be installed separately. A complete new installation package will not be required.
New installations: If possible, schedule new shop installations after the updated installation package has been released. Installation files downloaded earlier should then be replaced with the new version. The updated package can be identified by the date in its filename.
Note for modified 3.3.0: The newly announced security package has not yet been released and is therefore not included in the currently available MITS Module Update Pack. Once released, the additional security changes must be checked against existing module updates and individual shop customizations.
Our recommendation: Protect your store now with the available security fixes and prepare for the next update. If you need assistance, please use our contact form.
Following the recent security warnings affecting modified eCommerce Shopsoftware and the incident involving modified-shop.org, many store owners are asking what they should do now.
This practical guide from MerZ IT-SerVice outlines the most important immediate actions if your store may be affected and explains how to protect both your administration area and your store in the long term.
It is intended for all modified store owners, whether they maintain their stores themselves or use professional technical support.
Our Previous Security Reports
This guide complements our earlier publications. The following articles explain the incident, security fixes and latest findings:
Security Update of November 12, 2026
Which vulnerabilities were addressed, which store versions are affected and what should you check when applying the fixes?
Security Incident at modified-shop.org
Background on the manipulated newsfeed, the official warning of November 17 and further ways to protect your store.
For the latest official announcements, see modified eCommerce.
Latest Warning – November 17, 2026
On November 17, 2026, at 12:13 PM, the modified development team issued an additional security warning. Anyone logged into their store administration area on November 15, 2026, between 2:24 PM and 3:59 PM should treat the store as potentially compromised and complete all recommended actions.
The manipulated newsfeed could be stored in the store database. Opening affected administration pages later may also be dangerous while malicious content remains stored.
As early as November 15, 2026, our own investigations at MerZ IT-SerVice had identified the danger of malicious newsfeed content remaining in the database, and we developed protective measures. The subsequent official warning confirmed this assessment.
An active administrator session alone is not technical proof that malicious code was executed. Nevertheless, because of the potential consequences, the official warning must be taken seriously.
Important Information for Our Existing Customers
Have you already commissioned us to update and secure your store? We will carry out the agreed technical work for you. Depending on the scope of your order and store version, this may include:
- Installing appropriate security fixes while preserving existing customisations and modules.
- Cleaning potentially manipulated newsfeed content.
- Additional newsfeed protection in modified 3.3.0 using MITS Secure Newsfeed or the MITS Module Update Pack.
- Setting up or checking additional password protection for the administration directory.
- Reviewing key settings, administrator accounts and suspicious modifications within the agreed scope; we will contact you personally if we detect signs of compromise.
What you should do yourself: Change the passwords of all administrator accounts promptly. If we reset them, first use “Forgot password”, then replace the generated password with a new, long and randomly generated one.
If you used the same password for email, hosting or other services, change it there too. Keep the separate credentials for any additional directory password protection safe; they are required before your normal store login.
Immediate Security Actions: How to Proceed
If you maintain your store yourself and cannot rule out that it is affected, carry out the following actions carefully.
The sequence is guidance, not an inflexible checklist: if an attack is ongoing, containment and protecting access take priority; preserve evidence before cleanup whenever possible.
Warning: Do Not Open an Unsecured Administration Area!
Before cleaning and securing the store, avoid opening start.php or newsfeed.php. Malicious content stored in the database could execute in your browser when these pages display it.
For initial actions, use your hosting control panel, SFTP/SSH or external database administration rather than an unsecured administration dashboard.
1. Back Up the Current State and Preserve Evidence
Before making changes, preserve the current state of the store wherever possible:
- Store files: Make a complete copy via SFTP, SSH or your host’s file manager.
- Database: Create a full export through your hosting control panel or phpMyAdmin.
- Logs: Save available web server, PHP and access logs.
- Suspicious data: Document unusual files and database records before changing them.
Store backups securely outside the publicly accessible shop directory. If an attack is still in progress, effective containment is more important than lengthy evidence collection.
2. Add Temporary Protection to the Administration Area
Where possible, enable an additional access restriction before opening the administration area again. On Apache or compatible servers, password protection can use .htaccess and .htpasswd; nginx or other servers require the appropriate hosting or server configuration.
Verify that the password prompt actually appears and that authorised requests reach the store after authentication. Merely having a .htaccess file does not guarantee protection.
3. Remove Stored Newsfeed Entries
Potentially manipulated newsfeed records should be removed from the store database, preferably after preserving relevant evidence. In phpMyAdmin or an equivalent database tool, you can use the following SQL statement:
TRUNCATE TABLE `newsfeed`;Warning: This statement empties the table but does not delete the table itself. If your installation uses a database table prefix, use the actual table name. Run the statement only against the correct store database.
If you do not have direct database access, contact your hosting provider or technical service provider. Do not open an unsecured administration dashboard just to perform this cleanup.
Easier Newsfeed Cleanup with MITS Secure Newsfeed
For modified 3.3.0, the current MITS Secure Newsfeed module automatically removes stored newsfeed entries from the database when the module is successfully installed or updated. Manual cleanup in phpMyAdmin is then unnecessary for this specific step.
You can also disable the official newsfeed and other external administration dashboard content independently, while additional content security filtering remains active.
Important: Cleanup happens when installing or updating the module in the administration area, not simply when uploading its files. First ensure that administrator access is protected and that external content is displayed safely or disabled.
Important: Cleanup alone is insufficient if unsafe external content can subsequently be downloaded again. It does not replace security updates or investigation of a possible previous attack.
4. Install Security Fixes for Your Store Version
Apply the latest security fixes compatible with your specific modified version. Include the corrections published on November 13, 2026, including changes to inc/html_encoding.php for relevant versions.
- Back up the system and compare files before replacing them.
- Account for existing customisations and module updates.
- Never overwrite newer core changes with older files without checking.
- Verify file uploads and test orders, payments, email and administrator functions afterwards.
MITS Module Update Pack for modified 3.3.0
Our MITS Module Update Pack including Security Update brings together important updates for payment, shipping and other extensions with the current security fixes.
It already includes an additionally secured integration of the official modified newsfeed. Shared files are coordinated to help prevent one module update from unintentionally overwriting changes made by another.
5. Secure Administrator Accounts and Change Passwords
Once the administration area is safe to access, review all accounts. If credentials may have been stolen, restrict the affected access as early as possible.
- New passwords: Use a unique, randomly generated password of preferably 20–24 characters for every administrator account.
- Unknown accounts: Record and disable them first; remove them after investigation.
- Permissions: Grant employees only the administrator privileges they actually need.
- Admin email: Prefer a separate email address that is not publicly advertised.
- Other credentials: If there is evidence of exposure, rotate hosting, SFTP/SSH, email and API credentials and revoke existing sessions.
If an incident response reset the administrator passwords, use “Forgot password” initially, then replace the received password with a long, individually generated one.
6. Check Files for Malware and Unauthorised Changes
An attack may have left additional files or altered core files behind. Pay particular attention to:
- New or unexpectedly modified PHP files.
- Suspicious files in writable directories such as
imagesoruploads. - Modified configuration or core files and unknown extensions.
- Unusual permissions and suspicious administration tools.
Compare files with a trusted reference copy; legitimate module updates can also explain differences. A clean scan does not prove that a compromise never occurred.
Additional File Checks with MITS Security Center
MITS Security Center helps detect unexpected file changes, unusual permissions and suspicious files using checksum monitoring and heuristic malware checks. It does not replace a complete forensic investigation.
7. Review Store Settings and Payment Methods
After securing your store, check the following areas for unauthorised changes:
- Payments: Bank details, merchant accounts, recipient addresses and payment provider settings.
- API credentials: Issue new keys if you suspect exposure.
- Email: Check SMTP credentials and sender or recipient addresses.
- Store and extensions: Review redirects, configuration values, unknown modules and admin pages.
- Cache: Use the intended store and template cache functions after making changes.
When there are concrete signs of an incident, orders and customer data may also need to be reviewed for manipulation.
8. Document the Incident and Check Reporting Obligations
Document suspicious findings, dates and times, potentially affected data and all actions taken. If personal data may have been breached, assess any obligations under data protection law.
A reportable personal data breach generally needs to be notified to the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless a statutory exception applies. Seek professional or legal advice promptly when needed.
Essential Best Practices for a Secure Online Store
Immediate actions reduce current risks. Long-term protection also requires ongoing maintenance, trustworthy devices, strong access controls and reliable backups.
1. Keep Your Store, Extensions and PHP Updated
Security updates cover the shop core, payment, shipping and additional modules, templates and the PHP runtime. Regularly check which versions are supported.
For modified: Not every shop version supports the latest PHP version. Choose the highest PHP version officially supported by your shop and extensions that still receives security updates. An untested PHP change may break store functionality.
Which PHP Version Can You Use?
For modified 3.3.0, the officially supported range is currently PHP 8.0–8.4; PHP 8.5 is not yet officially supported. Older store versions may have lower maximum versions.
PHP 8.1 and earlier have reached official end of life; security support for PHP 8.2 ends on December 31, 2026. If your shop version cannot run on a current supported PHP version, plan an upgrade.
Check the modified compatibility matrix and PHP supported versions before changing PHP versions.
Your Legal Responsibilities
Article 32 of the GDPR requires appropriate technical and organisational measures to protect personal data. Neglecting security updates can have legal consequences. However, a security incident alone does not automatically establish a GDPR violation; the circumstances of the individual case matter.
2. Create Backups Using Generations and the 3-2-1 Rule
Reliable backups help with technical failures, data loss and security incidents. Keep recovery points for different periods:
- Daily backups: Restore recent orders and changes after a short-term problem.
- Weekly backups: Keep complete snapshots for several weeks.
- Monthly backups: Retain longer-term recovery points.
Also follow the 3-2-1 rule: three copies of your data, two independent storage types and at least one off-site copy. Ideally, at least one backup is protected against later modification or deletion.
Remember: Back up files and configuration as well as the database. Regularly test whether your backups can be restored successfully.
Automated Database Backups with MITS
MITS Cron Database Backups helps automate regular database backups. Your shop files must still be backed up separately.
3. Use Long, Unique Passwords
Weak or reused credentials increase the likelihood of successful attacks. For store and administrator accounts, we recommend:
- 20–24 characters or more for randomly generated administrator passwords.
- One password per service: Never reuse the same password for your shop, email, hosting and SFTP.
- Password managers: Generate and store credentials securely using a tool such as Bitwarden or KeePassXC.
- Individual accounts: Do not share employee logins; enable two-factor authentication wherever available.
Passwords do not need to be changed merely because they are old, but should be changed if they may have been exposed or reused.
4. Protect the Administration Area with Several Security Layers
Protect the administration area beyond the normal store login. The following measures are particularly useful:
- Enable Admin Token System: Under Configuration → Admin Area Options, ensure “Admin Token System” is set to Yes/true. Token validation helps protect important administrator actions against forged requests (CSRF). Depending on the shop version, working in multiple admin tabs may be restricted.
- Enable Admin Clickjacking Protection: In the same settings area, enable “Admin Clickjacking Protection”. The
X-Frame-Options: SAMEORIGINheader makes it harder for external websites to embed the admin interface. - Rename the admin directory: Replace the default
admindirectory name with an individual name. Afterwards, check directory paths, relevant configuration files, links and extensions. This makes automated discovery harder but does not replace real access controls. - Use a dedicated browser for store administration: Ideally use a separate, regularly updated browser only for shop and backend tasks. Do not open email or untrusted websites in it and avoid unnecessary extensions. A separate browser profile is a practical alternative.
- Additional password protection: Secure the admin directory using
.htaccess/.htpasswdor your host’s equivalent facility and verify that it works. - HTTPS and least privilege: Use HTTPS exclusively, remove unused accounts and grant only necessary administrator privileges.
Note: A dedicated browser and a renamed admin directory are additional layers, not guarantees against malicious code. Updates, newsfeed cleanup, token validation and access controls remain essential.
5. Run Regular Security Reviews
Periodically inspect key parts of your store installation:
- Unexpectedly created or modified files and suspicious access logs.
- File permissions and important PHP or server configuration values.
- Administrator accounts, permissions and installed extensions.
- Supported versions of the shop, modules, templates and dependencies.
MITS Security Center can help with checksum, malware and permission checks. Automated scans do not replace updates or expert investigation when compromise is suspected.
Conclusion: Store Security Is an Ongoing Responsibility
The current incident shows why secure external content integration, well-protected administrator access and reliable backups matter as much as keeping the software current.
Our recommendation: Review shop and PHP compatibility regularly, keep extensions updated, use a dedicated browser where possible and leave the built-in admin security features enabled.
If you suspect a compromise, follow a structured response: preserve important information, contain access and arrange a professional investigation when needed.
Need Help Securing Your modified Store?
We can help with security updates, newsfeed cleanup, reviewing your installation and protecting the administration area.
Secure your store professionally before a known risk becomes a serious incident.
Information status: November 18, 2026. Always check the latest modified security announcements and PHP compatibility information for your specific shop version.
