How severe is GHSA-xfg5-vrmc-24wc?

GHSA-xfg5-vrmc-24wc has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xfg5-vrmc-24wc?

GHSA-xfg5-vrmc-24wc affects the following packages: obsidian-dataview (npm). Ecosystems affected: npm.

How do I fix GHSA-xfg5-vrmc-24wc?

Update obsidian-dataview to 0.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xfg5-vrmc-24wc is resolved across your whole dependency graph.

How do I detect GHSA-xfg5-vrmc-24wc in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for obsidian-dataview. 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-xfg5-vrmc-24wc 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-xfg5-vrmc-24wc?

O3 pinpoints whether GHSA-xfg5-vrmc-24wc 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-xfg5-vrmc-24wc actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-xfg5-vrmc-24wc, 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 GHSA-xfg5-vrmc-24wc?

GHSA-xfg5-vrmc-24wc has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 64th 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 GHSA-xfg5-vrmc-24wc?

GHSA-xfg5-vrmc-24wc 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 GHSA-xfg5-vrmc-24wc published, and has it been updated?

GHSA-xfg5-vrmc-24wc was published on May 24, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-xfg5-vrmc-24wc

HIGH

Obsidian Dataview vulnerable to code injection due to unsafe eval

Also known asCVE-2021-42057

Published

May 24, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk64th percentile+0.91%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

obsidian-dataviewnpm

3Kdownloads / week

Description

Obsidian Dataview through 0.4.12-hotfix1 allows eval injection. The evalInContext function in executes user input, which allows an attacker to craft malicious Markdown files that will execute arbitrary code once opened. NOTE: 0.4.13 provides a mitigation for some use cases.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`obsidian-dataview`	all versions	0.4.13

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.

Obsidian Dataview through 0.4.12-hotfix1 allows eval injection. The eval…

github.comNVDNov 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for obsidian-dataview. 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 obsidian-dataview to 0.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xfg5-vrmc-24wc 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-xfg5-vrmc-24wc 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-xfg5-vrmc-24wc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Obsidian Dataview through 0.4.12-hotfix1 allows eval injection. The `evalInContext` function in executes user input, which allows an attacker to craft malicious Markdown files that will execute arbitrary code once opened. NOTE: 0.4.13 provides a mitigation for some use cases.

O3 Security · Impact-Aware SCA

Is GHSA-xfg5-vrmc-24wc in your dependencies?

O3 detects GHSA-xfg5-vrmc-24wc across npm 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