PT-2025-34241 · Laravel+1 · Laravel+1

Sn1P3Rt3S7

·

Published

2025-08-21

·

Updated

2025-08-21

·

CVE-2025-55744

CVSS v4.0

8.2

High

VectorAV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Name of the Vulnerable Software and Affected Versions: UnoPim versions prior to 0.2.1
Description: UnoPim, an open-source Product Information Management (PIM) system built on the Laravel framework, is susceptible to Cross-Site Request Forgery (CSRF) attacks. Certain endpoints lack appropriate CSRF protection, allowing an attacker to perform state-changing operations on behalf of an authenticated victim. Specifically, the /admin/catalog/products/copy/{id}, /admin/catalog/products/edit/{id}, /admin/catalog/categories/create, /admin/catalog/categories/edit/{id}, /admin/catalog/category-fields/create, /admin/catalog/category-fields/edit/{id}, /admin/catalog/attributes/create, and /admin/catalog/attributes/edit/{id} endpoints are vulnerable. The application uses the X-XSRF-TOKEN header for some endpoints, but it is missing in others. The vulnerability occurs because the vulnerable POST requests do not require the X-XSRF-TOKEN header and use either application/x-www-form-urlencoded or multipart/form-data content types, combined with cookies being sent due to the samesite attribute being set to None.
Recommendations:
  • Update to version 0.2.1 or later to resolve the issue.
  • Implement CSRF tokens for all state-changing requests.
  • Configure the samesite attribute to lax or strict to prevent CSRF attacks.
  • Ensure all state-changing requests are performed using the POST method instead of GET. If the product copy feature uses GET requests, set samesite to strict. Otherwise, samesite: lax should be sufficient.

Exploit

Fix

CSRF

Weakness Enumeration

CWE-352

Related Identifiers

CVE-2025-55744
GHSA-287X-6R2H-F9MW

Affected Products

Laravel
Unopim