How severe is GHSA-jmq3-x8q7-j9qm?

No CVSS score has been assigned to GHSA-jmq3-x8q7-j9qm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jmq3-x8q7-j9qm?

GHSA-jmq3-x8q7-j9qm affects the following packages: baserproject/basercms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-jmq3-x8q7-j9qm?

Update baserproject/basercms to 5.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmq3-x8q7-j9qm is resolved across your whole dependency graph.

How do I detect GHSA-jmq3-x8q7-j9qm 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-jmq3-x8q7-j9qm 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-jmq3-x8q7-j9qm?

O3 pinpoints whether GHSA-jmq3-x8q7-j9qm 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-jmq3-x8q7-j9qm actively exploited in the wild?

No public exploit code has been indexed for GHSA-jmq3-x8q7-j9qm 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-jmq3-x8q7-j9qm?

GHSA-jmq3-x8q7-j9qm has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th 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-jmq3-x8q7-j9qm?

GHSA-jmq3-x8q7-j9qm is classified as Cross-site Scripting (XSS) (CWE-79). 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-jmq3-x8q7-j9qm published, and has it been updated?

GHSA-jmq3-x8q7-j9qm was published on March 31, 2026 and was last updated on March 31, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-jmq3-x8q7-j9qm: baserproject/basercms Cross-Site Scripting

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk14th percentile+0.22%

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

baserCMS has a cross-site scripting vulnerability in blog posts.

Target

baserCMS 5.2.1 and earlier versions

Vulnerability

Malicious Javascript may be executed in blog posts.

Countermeasures

Update to the latest version of baserCMS

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

Credits

Gai Tanaka@Mitsui Bussan Secure Directions, Inc.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`baserproject/basercms`	all versions	5.2.3

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.
Fix
Update baserproject/basercms to 5.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmq3-x8q7-j9qm 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-jmq3-x8q7-j9qm 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-jmq3-x8q7-j9qm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

baserCMS has a cross-site scripting vulnerability in blog posts. ### Target baserCMS 5.2.1 and earlier versions ### Vulnerability Malicious Javascript may be executed in blog posts. ### Countermeasures Update to the latest version of baserCMS Please refer to the following page to reference for more information. https://basercms.net/security/JVN_20837860 ### Credits Gai Tanaka@Mitsui Bussan Secure Directions, Inc.

O3 Security · Impact-Aware SCA

Is GHSA-jmq3-x8q7-j9qm in your dependencies?

O3 detects GHSA-jmq3-x8q7-j9qm 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

GHSA-jmq3-x8q7-j9qm