How severe is GHSA-vrm6-c878-fpq6?

GHSA-vrm6-c878-fpq6 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vrm6-c878-fpq6?

GHSA-vrm6-c878-fpq6 affects the following packages: baserproject/basercms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-vrm6-c878-fpq6?

No patched version of baserproject/basercms has shipped for GHSA-vrm6-c878-fpq6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-vrm6-c878-fpq6 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for baserproject/basercms. 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-vrm6-c878-fpq6 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-vrm6-c878-fpq6?

O3 pinpoints whether GHSA-vrm6-c878-fpq6 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-vrm6-c878-fpq6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vrm6-c878-fpq6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vrm6-c878-fpq6?

GHSA-vrm6-c878-fpq6 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 43th 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.

When was GHSA-vrm6-c878-fpq6 published, and has it been updated?

GHSA-vrm6-c878-fpq6 was published on October 26, 2023 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.

🐘 Packagist

GHSA-vrm6-c878-fpq6

MEDIUM

baserCMS Code Injection Vulnerability in Mail Form Feature

Also known asCVE-2023-43792

Published

Oct 26, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk43th percentile+0.23%

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

🐘baserproject/basercms

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

There is a Code Injection Vulnerability in Mail Form to baserCMS.

Target

baserCMS 4.7.6 and earlier versions

Vulnerability

Malicious code may be executed in Mail Form Feature.

Countermeasures

Update to the latest version of baserCMS

Please refer to the following page to reference for more information. https://basercms.net/security/JVN_45547161

Credits

Shiga Takuma@BroadBand Security, Inc

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`baserproject/basercms`	≥ 4.6.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for baserproject/basercms. 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.
Remediation status
No patched version of baserproject/basercms has shipped for GHSA-vrm6-c878-fpq6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-vrm6-c878-fpq6 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-vrm6-c878-fpq6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

There is a Code Injection Vulnerability in Mail Form to baserCMS. ### Target baserCMS 4.7.6 and earlier versions ### Vulnerability Malicious code may be executed in Mail Form Feature. ### Countermeasures Update to the latest version of baserCMS Please refer to the following page to reference for more information. https://basercms.net/security/JVN_45547161 ### Credits Shiga Takuma@BroadBand Security, Inc

O3 Security · Impact-Aware SCA

Is GHSA-vrm6-c878-fpq6 in your dependencies?

O3 detects GHSA-vrm6-c878-fpq6 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