ps_contactinfo has a potential XSS due to usage of the nofilter tag in template
Published 22 Jan 2025 · Updated 22 Jan 2025
Is your project on an affected prestashop/ps_contactinfo?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <3.3.3
- Fixed in
- 3.3.3
composer require prestashop/ps_contactinfo:^3.3.3Details
Impact
This can not be exploited in a fresh install of PrestaShop, only shops made vulnerable by third party modules are concerned.
For example, if your shop has a third party module vulnerable to SQL injections, then ps_contactinfo might execute a stored XSS in FO.
Patches
The long term fix is to have all your modules maintained and updated. The fix on ps_contactinfo will keep formatted addresses from displaying an xss stored in the database.
Workarounds
none
References
none
Is GHSA-35pq-7pv2-2rfw in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected prestashop/ps_contactinfo, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.