# CVE-2021-43852: JavaScript Prototype Pollution in oro/platform

> Attackers can inject properties into JavaScript prototypes via crafted requests, potentially leading to code execution in vulnerable libraries.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jan 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-jx5q-g37m-h5hj

## What is CVE-2021-43852?

CVE-2021-43852 is a high-severity code injection vulnerability in oroinc platform, published on 4 Jan 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OroPlatform is a PHP Business Application Platform. In affected versions by sending a specially crafted request, an attacker could inject properties into existing JavaScript language construct prototypes, such as objects. Later this injection may lead to JS code execution by libraries that are vulnerable to Prototype Pollution. This issue has been patched in version 4.2.8. Users unable to upgrade may configure a firewall to drop requests containing next strings: `__proto__` , `constructor[prototype]`, and `constructor.prototype` to mitigate this issue.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2021-43852?

4 open source packages ship an affected version, including oro/platform. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oro/platform` | Packagist | From 4.1.0 | 4.1.14 |
| `oro/platform` | Packagist | From 4.1.0 | 4.1.14 |
| `oro/platform` | Packagist | From 4.2.0 | 4.2.8 |
| `oro/platform` | Packagist | From 4.2.0 | 4.2.8 |

Products: Oroinc Oroplatform.

## How do I fix CVE-2021-43852?

Upgrade oro/platform to a fixed version for your release line: 4.1.14 or 4.2.8.

## Is CVE-2021-43852 being exploited?

There is no known exploitation of CVE-2021-43852 in the wild and no public exploit code.

## Other vulnerabilities in oroinc platform

- [CVE-2022-41951](https://insights.sbomify.com/CVE-2022-41951/): OroPlatform vulnerable to path traversal during temporary file manipulations (high 8.6)
- [CVE-2021-41236](https://insights.sbomify.com/CVE-2021-41236/): XSS vulnerability in oro/platform (medium 6.9)
- [CVE-2024-50677](https://insights.sbomify.com/CVE-2024-50677/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2023-32062](https://insights.sbomify.com/CVE-2023-32062/): OroCalendarBundle has incorrect system calendar events visibility (medium 5.0)
- [CVE-2023-45824](https://insights.sbomify.com/CVE-2023-45824/): OroPlatform's pinned entity creation form shows pages of other users (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43852 and fix it if it is affected.

What it is: CVE-2021-43852 is a high-severity code injection vulnerability in oroinc platform, published on 4 Jan 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-43852 in the wild and no public exploit code.

Affected packages and fixed versions:
- oro/platform (Packagist): affected from 4.1.0; fixed in 4.1.14
- oro/platform (Packagist): affected from 4.1.0; fixed in 4.1.14
- oro/platform (Packagist): affected from 4.2.0; fixed in 4.2.8
- oro/platform (Packagist): affected from 4.2.0; fixed in 4.2.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-43852/ (Markdown: https://insights.sbomify.com/CVE-2021-43852/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-43852
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-43852
- OSV: https://osv.dev/vulnerability/CVE-2021-43852

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-43852/
Summaries are generated and may contain mistakes; the official description above is the record.