zipMoney(Zip Co) Payments: security vulnerability
zipMoney(Zip Co) Payments
Security vulnerability in the zipMoney(Zip Co) Payments component. Threat level: Critical (CVSS 9.1).
Who is affected
This vulnerability affects: zipMoney(Zip Co) Payments. If you use this component on your site, check the version and update it as soon as possible.
How dangerous
Rating: Critical, CVSS 9.1 out of 10. Critical flaws are often exploited en masse within hours of disclosure.
What this flaw is
This is a security vulnerability in one of the site components. Full technical details are described in the source NVD entry, linked below.
Even seemingly lower-priority flaws are often chained into attacks, so it is not worth delaying the update of the vulnerable component.
Score breakdown (CVSS vector)
What the CVSS 9.1 rating means in practice:
- The attack can be carried out remotely, over the internet.
- No login or account required.
- Requires no action from the victim.
- At risk: integrity (data can be altered), site availability.
Weakness class: CWE-862.
How to fix: security vulnerability
- Update the vulnerable component to the latest version.
- If a patch is not out yet, temporarily disable the vulnerable element.
- Check whether the site has already been attacked: unusual files, new administrator accounts, redirects.
- Make a backup before you start making changes.
Prefer not to do this yourself? We will handle the update, check for signs of a break-in and secure the site. Write to us →
Frequently asked questions
Does this vulnerability affect my site?
It affects sites that use zipMoney(Zip Co) Payments. Check whether you have this component installed and which version, the flaw only applies to the vulnerable version range. You can verify it in under a minute with our free vulnerability scanner.
How do I check whether I have the vulnerable version?
In your admin panel (in WordPress: Plugins / Themes) check the installed version of zipMoney(Zip Co) Payments and compare it with the vendor advisory that names the fixed version. If it is lower, or you are not sure, run our scanner, which reads the versions visible in the site code.
How urgently should I react?
This is a Krytyczna-severity flaw, so treat it as urgent, high-impact vulnerabilities are often exploited automatically within hours of disclosure. Update as soon as possible.
What if a patch is not available yet?
Until a fix ships, reduce the exposure: temporarily disable the vulnerable component, restrict access to the affected functionality, or add a WAF rule blocking the vulnerable request. Keep a current off-site backup and watch for signs of a break-in.
Is updating alone enough?
If the site has not been attacked yet, updating to the patched version closes the hole. If there are already signs of compromise (unknown files, new admin accounts, redirects), the update does not undo the break-in, you also need to clean the site and rotate passwords and the WordPress salts.
Does this flaw affect your site?
We will run a free audit: we check versions, plugins, and configuration, and tell you plainly whether you are safe.
Request a free audit →