CVE-2022-48366: An issue was discovered in eZ Platform Ibexa Kernel before 1.3.19.
Noroxi assessment
Priority: Monitor (action score 14/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: ezsystems/ezplatform-kernel (Packagist) 1.3.19; ezsystems/ezpublish-kernel (Packagist) 7.5.29.
Low priority for now. Upgrade to ezsystems/ezplatform-kernel (Packagist) 1.3.19; ezsystems/ezpublish-kernel (Packagist) 7.5.29 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in eZ Platform Ibexa Kernel before 1.3.19. It allows determining account existence via a timing attack.
- Published
- Mar 12, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-362
Report tools
Action score
14
Low priority for now.
- CVSS
- 14 / 40 · 3.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ibexa | commerce | cpe:2.3:a:ibexa:commerce |
| ibexa | digital experience platform | cpe:2.3:a:ibexa:digital_experience_platform |
| ibexa | ez platform | cpe:2.3:a:ibexa:ez_platform |
| ibexa | ezplatform-page-builder | cpe:2.3:a:ibexa:ezplatform-page-builder |
| ibexa | jmspaymentcorebundle | cpe:2.3:a:ibexa:jmspaymentcorebundle |
| ibexa | ez platform kernel | cpe:2.3:o:ibexa:ez_platform_kernel |
| ibexa | kernel | cpe:2.3:o:ibexa:kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibexa commerce2.5.0 and later · before 2.5.13
- ibexa commerce3.3.0 and later · before 3.3.18
- ibexa commerce4.0.0 and later · before 4.0.7
- ibexa commerce4.1.0 and later · before 4.1.4
- ibexa digital experience platform3.3.0 and later · before 3.3.20
- ibexa digital experience platform4.0.0 and later · before 4.0.7
- ibexa digital experience platform4.1.0 and later · before 4.1.4
- ibexa ez platformbefore 2.5.30
+7 more rows
- ibexa ez platform kernel1.3.0 and later · before 1.3.19
- ibexa ez platform kernel7.5.0 and later · before 7.5.29
- ibexa ezplatform-page-builder1.3.0 and later · before 1.3.27
- ibexa ezplatform-page-builder2.3.0 and later · before 2.3.19
- ibexa jmspaymentcorebundle3.0.0 and later · before 3.0.2
- ibexa kernel4.1.0 and later · before 4.1.4
- ibexa kernel4.0.0 and later · before 4.0.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | ezsystems/ezplatform-kernel | from 1.3.0 · before 1.3.19 | 1.3.19 |
| Packagist | ezsystems/ezpublish-kernel | from 7.5.0 · before 7.5.29 | 7.5.29 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:ezsystems/ezplatform-kernel | 1.3.19 | Package registry (OSV) |
| Packagist:ezsystems/ezpublish-kernel | 7.5.29 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.