# CVE-2026-7380: HTML Injection in Armiya Technologies' Access Control System

> An attacker can inject malicious HTML attributes into the Access Control System web interface, potentially executing scripts or hijacking user sessions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-mfw3-p4vm-vmhx

## What is CVE-2026-7380?

CVE-2026-7380 is a medium-severity cross-site scripting vulnerability in Armiya Information Technologies Ltd. Co. Access Control System (GKS), published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper neutralization of Script-Related HTML tags in a web page (basic XSS) vulnerability in Armiya Information Technologies Ltd. Co. Access Control System (GKS) allows XSS Targeting HTML Attributes.

This issue affects Access Control System (GKS): before Version 2.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2026-7380?


## How do I fix CVE-2026-7380?

No fix has been published for CVE-2026-7380 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7380 being exploited?

There is no known exploitation of CVE-2026-7380 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7380 and fix it if it is affected.

What it is: CVE-2026-7380 is a medium-severity cross-site scripting vulnerability in Armiya Information Technologies Ltd. Co. Access Control System (GKS), published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-7380 in the wild and no public exploit code.

Affected product: Armiya Information Technologies Ltd. Co. Access Control System (GKS). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7380/ (Markdown: https://insights.sbomify.com/CVE-2026-7380/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7380
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7380
- OSV: https://osv.dev/vulnerability/CVE-2026-7380

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7380/
Summaries are generated and may contain mistakes; the official description above is the record.