How severe is CVE-2022-46157?

CVE-2022-46157 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-46157?

CVE-2022-46157 affects the following packages: akeneo/pim-community-dev (Packagist), akeneo/pim-community-dev (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-46157?

Update akeneo/pim-community-dev to 6.0.53 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-46157 is resolved across your whole dependency graph.

How do I detect CVE-2022-46157 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for akeneo/pim-community-dev, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-46157 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2022-46157 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-46157, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-46157?

CVE-2022-46157 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-46157?

CVE-2022-46157 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-46157 published, and has it been updated?

CVE-2022-46157 was published on December 9, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2022-46157 — pim-community-dev

HIGHFix: akeneo/pim-community-dev@891a2f7

CVE-2022-46157 is a high-severity (CVSS 8.8) Code Injection vulnerability in akeneo/pim-community-dev. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for akeneo/pim-community-dev — see the affected versions and patch details below.

Remote php code execution in Akeneo PIM

Also known asBIT-akeneo-2022-46157GHSA-w9wc-4xcq-8gr6

Published

Dec 9, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Oct 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk+0.05%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘akeneo/pim-community-dev🐘akeneo/pim-community-dev

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

Akeneo PIM Community Edition versions before v5.0.119 and v6.0.53 allows remote authenticated users to execute arbitrary PHP code on the server by uploading a crafted image.

Patches

Akeneo PIM Community Edition after the versions aforementioned provides patched Apache HTTP server configuration file, for docker setup and in documentation sample, to fix this vulnerability.
Community Edition users must change their Apache HTTP server configuration accordingly to be protected. The patch for Cloud Based Akeneo PIM Services customers has been applied since 30th October 2022.

Workarounds

Replace any reference to <FilesMatch \.php$> in your apache httpd configurations with: <Location "/index.php">, as shown in https://github.com/akeneo/pim-community-dev/blob/b4d79bb073c8b68ea26ab227c97cc78d86c4cba1/docker/httpd.conf#L39.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`akeneo/pim-community-dev`	≥ 6.0.0&&< 6.0.53	6.0.53`composer require akeneo/pim-community-dev:^6.0.53`
🐘Packagist	`akeneo/pim-community-dev`	all versions	5.0.119`composer require akeneo/pim-community-dev:^5.0.119`

Affected Products

1 product · 2 configurations

Application

product information managementakeneo

≥ 6.0.0 && < 6.0.53

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Akeneo PIM is an open source Product Information Management (PIM). Akene…

github.comNVDDec 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for akeneo/pim-community-dev, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update akeneo/pim-community-dev to 6.0.53 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-46157 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact Akeneo PIM Community Edition versions before v5.0.119 and v6.0.53 allows remote authenticated users to execute arbitrary PHP code on the server by uploading a crafted image. ### Patches Akeneo PIM Community Edition after the versions aforementioned provides patched Apache HTTP server configuration file, for docker setup and in documentation sample, to fix this vulnerability. Community Edition users must change their Apache HTTP server configuration accordingly to be protected. The patch for Cloud Based Akeneo PIM Services customers has been applied since 30th October 2022. ##