Summary
UnoPim vulnerable to CSRF on Product edit feature and creation of other types
Impact
Attacker can perform action on behalf of the victim as this happens on the victim's browser provide the victim is already authenticated to the application.
Attacker can use an image tag to send the GET request such that when the page is loaded, it'll get executed.
As shown in the video POC, the product information can be tampered, create new categories etc.
A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
- Use CSRF token for every state changing request.
- Use samesite: lax or strict, now it is set 'None'. Make sure all state changing requests are done using POST instead of GET. Noticed that for product copy feature, GET is used which means Samesite:strict needs to be set in that case. Otherwise Samesite: lax should suffice.
Frequently Asked Questions
- What is CVE-2025-55744? CVE-2025-55744 is a medium-severity cross-site request forgery (CSRF) vulnerability in unopim/unopim (composer), affecting versions <= 0.2.0. It is fixed in 0.2.1. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
- Which versions of unopim/unopim are affected by CVE-2025-55744? unopim/unopim (composer) versions <= 0.2.0 is affected.
- Is there a fix for CVE-2025-55744? Yes. CVE-2025-55744 is fixed in 0.2.1. Upgrade to this version or later.
- Is CVE-2025-55744 exploitable, and should I be worried? Whether CVE-2025-55744 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-55744 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-55744? Upgrade
unopim/unopimto 0.2.1 or later.