How severe is CVE-2023-29918?

CVE-2023-29918 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-29918?

CVE-2023-29918 affects the following packages: francoisjacquet/rosariosis (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2023-29918?

No patched version of francoisjacquet/rosariosis has shipped for CVE-2023-29918 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 CVE-2023-29918 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for francoisjacquet/rosariosis. 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 CVE-2023-29918 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 CVE-2023-29918?

O3 pinpoints whether CVE-2023-29918 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 CVE-2023-29918 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2023-29918, including 1 documented proof-of-concept exploit on Exploit-DB and 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-2023-29918?

CVE-2023-29918 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 80th 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 CVE-2023-29918 published, and has it been updated?

CVE-2023-29918 was published on May 2, 2023 and was last updated on April 10, 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

CVE-2023-29918

MEDIUM

RosarioSIS vulnerable to CSV Injection

Also known asGHSA-f8hp-grmr-pp7j

Published

May 2, 2023

Updated

Apr 10, 2026

Affected

1 pkg

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk80th percentile-3.67%

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

🐘francoisjacquet/rosariosis

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

RosarioSIS 10.8.4 is vulnerable to CSV injection via the Periods Module.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`francoisjacquet/rosariosis`	all versions	No fix

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.

EDB-51622webappsphp✓ Verified

RosarioSIS 10.8.4 - CSV Injection

by Ranjeet Jaiswal · Jul 28, 2023

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for francoisjacquet/rosariosis. 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 francoisjacquet/rosariosis has shipped for CVE-2023-29918 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 CVE-2023-29918 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 CVE-2023-29918. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

RosarioSIS 10.8.4 is vulnerable to CSV injection via the Periods Module.

O3 Security · Impact-Aware SCA

Is CVE-2023-29918 in your dependencies?

O3 detects CVE-2023-29918 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

CVE-2023-29918

EPSS Exploitation Probability

Blast Radius

Description

Affected Packages

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2023-29918 in your dependencies?