The library automation system product KOHA developed by Parantez Teknoloji before version 19.05.03 has an unauthenticated SQL Injection vulnerability. This has been fixed in the version 19.05.03.01.
Security readout for executives and security teams
Plain-English summary
CVE-2022-0495 is a critical unauthenticated SQL injection in the KOHA library automation system developed by Parantez Teknoloji before version 19.05.03. A remote attacker may be able to access or alter database data without logging in. The cited record says it is fixed in version 19.05.03.01.
Executive priority
Treat as urgent for any exposed Parantez Teknoloji KOHA instance. The issue is critical, unauthenticated, and database-impacting. Prioritize version verification and upgrade planning, especially where library patron, staff, or operational data is stored.
Technical view
The CVE describes CWE-89 SQL injection, network exploitable with low complexity, no privileges, and no user interaction. CVSS 3.1 is 9.4, with high confidentiality and integrity impact and low availability impact. Public sources do not identify the vulnerable parameter, endpoint, or proof-of-concept details.
Likely exposure
Exposure is likely limited to organizations running Parantez Teknoloji’s KOHA deployment before version 19.05.03, especially if reachable from untrusted networks. The source data does not provide CPEs, deployment indicators, or affected endpoint details.
Exploitation context
No cited source or KEV listing indicates active exploitation. However, unauthenticated SQL injection in an internet-facing application is typically high-risk because it can expose sensitive database records and enable data tampering.
Researcher notes
The public record is sparse. It confirms unauthenticated SQL injection and fixed version 19.05.03.01, but not the vulnerable route, parameter, or exploit maturity. One listed government reference is tagged as broken in the provided bundle; validate against the accessible advisory and CVE record.
Mitigation direction
Upgrade affected KOHA installations to version 19.05.03.01 as cited by the CVE record.
If upgrade timing is unclear, check current vendor or government advisory guidance.
Restrict public access to the application where business requirements allow.
Review database and application logs for unusual unauthenticated activity.
Validation and detection
Inventory KOHA deployments and identify any Parantez Teknoloji-maintained instances.
Confirm installed version is 19.05.03.01 or a vendor-confirmed fixed release.
Verify whether any instance is reachable from the internet or untrusted networks.
Check advisories for updated affected-version or remediation details.
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.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
1CVSS vectors
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.