How severe is GHSA-j8cx-j9j2-f29w?

No CVSS score has been assigned to GHSA-j8cx-j9j2-f29w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j8cx-j9j2-f29w?

GHSA-j8cx-j9j2-f29w affects the following packages: microweber/microweber (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-j8cx-j9j2-f29w?

Update microweber/microweber to 1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8cx-j9j2-f29w is resolved across your whole dependency graph.

How do I detect GHSA-j8cx-j9j2-f29w in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for microweber/microweber. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-j8cx-j9j2-f29w if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-j8cx-j9j2-f29w?

O3 pinpoints whether GHSA-j8cx-j9j2-f29w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-j8cx-j9j2-f29w actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-j8cx-j9j2-f29w, 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 type of vulnerability is GHSA-j8cx-j9j2-f29w?

GHSA-j8cx-j9j2-f29w is classified as CWE-922 (CWE-922). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j8cx-j9j2-f29w published, and has it been updated?

GHSA-j8cx-j9j2-f29w was published on February 24, 2022 and was last updated on December 5, 2024. 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

GHSA-j8cx-j9j2-f29w

Fix: microweber/microweber@b592c86

GHSA-j8cx-j9j2-f29w is a CWE-922 vulnerability in microweber/microweber. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-j8cx-j9j2-f29w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Insecure Storage of Sensitive Information in Microweber

Also known asCVE-2022-0724

Published

Feb 24, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Dec 5, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘microweber/microweber

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

Microweber prior to version 1.3 does not strip images of EXIF data, exposing information about users' locations, device hardware, and device software.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`microweber/microweber`	all versions	1.3

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.

Insecure Storage of Sensitive Information in GitHub repository microwebe…

huntr.devNVDMar 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for microweber/microweber. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update microweber/microweber to 1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8cx-j9j2-f29w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-j8cx-j9j2-f29w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-j8cx-j9j2-f29w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Microweber prior to version 1.3 does not strip images of EXIF data, exposing information about users' locations, device hardware, and device software.

O3 Security · Impact-Aware SCA

Is GHSA-j8cx-j9j2-f29w in your dependencies?

O3 detects GHSA-j8cx-j9j2-f29w across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works