LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34134: Jorani v1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /application/co...

Jorani v1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /application/controllers/Users.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-34134 is a reported CSRF flaw in Jorani v1.0 involving the Users.php controller. In business terms, a logged-in user could potentially be tricked into causing an unintended user-management action. The public bundle does not provide CVSS scoring, confirmed impact details, or evidence of active exploitation.

Executive priority

Treat this as a targeted application hygiene item rather than an emergency based on current evidence. Prioritize if Jorani v1.0 is used for workforce or leave-management workflows with privileged user administration exposed to many authenticated users.

Technical view

The CVE description identifies Cross-Site Request Forgery in Jorani v1.0 through /application/controllers/Users.php. The available references are a GitHub issue and an upstream commit. The source bundle does not include affected CPEs, CWE mapping, CVSS metrics, or a named fixed release.

Likely exposure

Exposure is most likely limited to organizations running Jorani v1.0 where the application is reachable by authenticated users through a browser. The source bundle lists affected vendor and product fields as n/a, so inventory should verify product and version from deployment records.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not claim active exploitation. As a CSRF issue, practical risk typically depends on an authenticated user's browser being induced to send an unintended request, but exact affected actions are not established in the bundle.

Researcher notes

Evidence is thin: the CVE record names CSRF in Users.php, but does not provide CVSS, CWE, affected CPEs, proof of exploitation, or a fixed release name. The GitHub issue and commit are the key artifacts for confirming root cause and patch coverage.

Mitigation direction

  • Check the upstream issue and commit for vendor-confirmed remediation details.
  • Identify whether deployed Jorani instances are version 1.0.
  • Update to a vendor-confirmed fixed release if one is available.
  • Limit access to Jorani user-management functions while remediation is pending.
  • Confirm CSRF protections are present in user-management request handling.

Validation and detection

  • Inventory public and internal Jorani deployments and record versions.
  • Review deployed Users.php against the referenced upstream commit.
  • Check whether user-management forms require valid CSRF protection.
  • Review access logs for unusual user-management changes around authenticated sessions.
  • Document findings and remediation status in the vulnerability register.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-34134 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.