How severe is CVE-2022-1848?

CVE-2022-1848 has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-1848?

CVE-2022-1848 affects the following packages: com.erudika:para-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-1848?

Update com.erudika:para-core to 1.46.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1848 is resolved across your whole dependency graph.

How do I detect CVE-2022-1848 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.erudika:para-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-1848 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.

Is CVE-2022-1848 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-1848, 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 CVE-2022-1848?

CVE-2022-1848 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th 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 CVE-2022-1848?

CVE-2022-1848 is classified as CWE-840 (CWE-840). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-1848 published, and has it been updated?

CVE-2022-1848 was published on May 24, 2022 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2022-1848 — para-core

CRITICALFix: erudika/para@fa677c6

CVE-2022-1848 is a critical-severity (CVSS 9) CWE-840 vulnerability in com.erudika:para-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.erudika:para-core — see the affected versions and patch details below.

Business Logic Errors in erudika/para

Also known asGHSA-4793-8wwh-jxxr

Published

May 24, 2022

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕com.erudika:para-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Paraara prior to version 1.46.0 is vulnerable to business logic errors. A user can create more than one app, even after they reach the app limit.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.erudika:para-core`	all versions	1.46.0`com.erudika:para-core:1.46.0`

Affected Products

1 product · 1 configurations

Application

paraerudika

< 1.45.11

range

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.

Business Logic Errors in GitHub repository erudika/para prior to 1.45.11…

huntr.devNVDJun 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.erudika:para-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.erudika:para-core to 1.46.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1848 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.

Frequently Asked Questions

Paraara prior to version 1.46.0 is vulnerable to business logic errors. A user can create more than one app, even after they reach the app limit.

O3 Security · Impact-Aware SCA

Is CVE-2022-1848 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

CWE Classification

CWE-840CWE-840

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

May 24, 2022

First exploit

Jun 3, 2022

Last updated

Oct 21, 2026

Identifiers

CVE-2022-1848

GHSA-4793-8wwh-jxxr

References

Advisorygithub.com · CVE 2022 1848.json Advisorynvd.nist.gov · CVE 2022 1848 Fixgithub.com · fa677c629842df60099daa9c23bd802bc41b48d1 Webhuntr.dev · 8dfe0877 e44b 4a1a 8eee 5c03c93ae90a Packagegithub.com · para

Related vulnerabilities

This CVE is critical severity, in line with the other 1 CVE affecting para-core.

CVE-2022-1782

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 21, 2026

CVE-2022-1848 — para-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-1848 in your dependencies?