Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-35pq-7pv2-2rfw

MEDIUMFix: PrestaShop/ps_contactinfo@d60f9a5

GHSA-35pq-7pv2-2rfw is a medium-severity (CVSS 6.2) Cross-site Scripting (XSS) vulnerability in prestashop/ps_contactinfo. O3 Security confirms whether GHSA-35pq-7pv2-2rfw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

ps_contactinfo has a potential XSS due to usage of the nofilter tag in template

Also known asCVE-2025-24027
Published
Jan 22, 2025
Updated
Jan 22, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jan 22, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘prestashop/ps_contactinfo

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistprestashop/ps_contactinfoall versions3.3.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for prestashop/ps_contactinfo. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update prestashop/ps_contactinfo to 3.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-35pq-7pv2-2rfw is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-35pq-7pv2-2rfw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-35pq-7pv2-2rfw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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
O3 Security · Impact-Aware SCA

Is GHSA-35pq-7pv2-2rfw in your dependencies?

O3 detects GHSA-35pq-7pv2-2rfw across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-35pq-7pv2-2rfw: prestashop/ps_contact… | O3 Security