Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-85520 – Unauthenticated RCE via Arbitrary File Write – Google Merchant Center Feed (gmfeed)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-85520 is a critical unauthenticated arbitrary file write vulnerability in the Google Merchant Center Feed (gmfeed) module for PrestaShop, developed by MyPresta. The flaw resides in the module’s feed.php endpoint, which fails to enforce authentication or validate attacker-supplied parameters that control the name, path, extension, and content of files written to the server. By submitting a crafted request, an unauthenticated attacker can write a PHP file to a web-accessible location and have it executed, resulting in full remote code execution (RCE) on the underlying store.

Technical details

  • Root cause: External control of file name or path (CWE-73) — the feed.php endpoint accepts request parameters that directly determine the output file’s name, directory path, and extension without sanitization or access control checks.
  • Trigger conditions: The module must be configured to generate catalog feeds via URL with the "save to file" option enabled; no valid session, API key, or credentials are required to reach the vulnerable endpoint.
  • Attack vector: Network-based, unauthenticated, low complexity — a single crafted HTTP request to feed.php is sufficient to plant a file.
  • Impact: Because the attacker fully controls the file extension and content, a .php file containing attacker-supplied code can be written into the webroot and subsequently invoked, giving the attacker arbitrary PHP code execution in the context of the web server (full compromise of confidentiality, integrity, and availability of the store and any data it processes, e.g. customer and payment-related data).

Affected software

  • Google Merchant Center Feed (gmfeed) module for PrestaShop, versions 1.9.1 through 2.3.8 (per the CVE record)
  • The vendor advisory further recommends any release below 2.3.10 be considered unsafe and upgraded

Severity

  • CVSS v4.0 Base Score: 9.3 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L
  • Key drivers: network attack vector, no privileges or user interaction required, and high impact to confidentiality, integrity, and availability.

Mitigation and recommended actions

  • Immediate: Upgrade the gmfeed module to version 2.4.1 (the vendor’s advisory states 2.3.10 is the minimum patched version, with 2.4.1 as the current recommended release). Do not simply overwrite files — fully uninstall the existing module (including deleting old module files via the "delete module files" option in Module Manager) before installing the new package to ensure no vulnerable code remains.
  • After upgrading: Regenerate and replace any feed "Generate"/cron URLs used for save-to-file feed generation, since previously issued URLs are invalidated by the fix, and update any external integrations (cron jobs, Google Merchant Center feed URLs) accordingly.
  • If immediate patching is not possible: Disable the "save to file" / URL-based feed generation feature of the module, restrict or block external access to feed.php at the web server or WAF layer, and monitor the store’s file system and webroot for unexpected newly created PHP files.
  • General hygiene: Review server logs for anomalous POST/GET requests to feed.php predating the patch, and scan the PrestaShop installation for unauthorized files that may already have been planted.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge