CVE-2023-5321

CVE-2023-5321 is a medium-severity vulnerability in Hamza417 Inure with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-862.

Key facts

• Severity: Medium (CVSS 3.x base score 5.5)
• EPSS exploit prediction: 0% (17th percentile)
• Actively exploited: Not listed in CISA KEV
• Weakness: CWE-862
• Affected product: Hamza417 Inure
• Published: 2023-09-30
• Last modified: 2026-06-17

Description

Missing Authorization in GitHub repository hamza417/inure prior to build94.

Frequently asked questions

What is CVE-2023-5321?

Missing Authorization in GitHub repository hamza417/inure prior to build94.

How severe is CVE-2023-5321?

CVE-2023-5321 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2023-5321 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2023-5321?

CVE-2023-5321 primarily affects Hamza417 Inure. In total, 43 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2023-5321?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2023-5321 published?

CVE-2023-5321 was published on 2023-09-30 and last updated on 2026-06-17.

References

• https://github.com/hamza417/inure/commit/57fda918bfd2fb863f579841a46363fe8e10c29b
• https://huntr.dev/bounties/b1becc68-e738-458f-bd99-06ee77580d3a

Affected products (43)

• cpe:2.3:a:hamza417:inure:build44:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build45:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build46:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build47:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build48:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build49:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build51:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build52:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build53:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build55:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build56:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build57:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build58:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build59:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build60:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build61:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build62:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build63:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build64:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build65:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build66:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build67:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build68:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build69:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build70:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build71:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build72:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build73:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build74:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build75:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build76:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build77:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build78:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build79:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build80:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build83:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build85:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build86:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build87:*:*:*:*:android:*:*
• cpe:2.3:a:hamza417:inure:build88:*:*:*:*:android:*:*

More vulnerabilities in Hamza417 Inure

• CVE-2023-4877 — High (CVSS 7.5): Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository hamza417/inure prior to build92.
• CVE-2023-4876 — High (CVSS 7.5): Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository hamza417/inure prior to build92.
• CVE-2023-4434 — Medium (CVSS 6.1): Missing Authorization in GitHub repository hamza417/inure prior to build88.
• CVE-2023-4435 — Medium (CVSS 5.5): Improper Input Validation in GitHub repository hamza417/inure prior to build88.
• CVE-2023-5862 — Low (CVSS 3.3): Missing Authorization in GitHub repository hamza417/inure prior to Build95.

All CVEs affecting Hamza417 Inure →

Other CWE-862 (Missing Authorization) vulnerabilities

• CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
• CVE-2026-33712 — Critical (CVSS 10.0): Typebot is a chatbot builder tool. In versions 3.15.2 and prior, the preview chat endpoint (POST…
• CVE-2026-2031 — Critical (CVSS 10.0): An Improper Access Control vulnerability in several internal API endpoints for Google Cloud Application Integration…
• CVE-2026-34976 — Critical (CVSS 10.0): Dgraph is an open source distributed GraphQL database. Prior to 25.3.1, the restoreTenant admin mutation is missing…
• CVE-2025-30416 — Critical (CVSS 10.0): Sensitive data disclosure and manipulation due to missing authorization. The following products are affected: Acronis…
• CVE-2025-45854 — Critical (CVSS 10.0): /server/executeExec of JEHC-BPM 2.0.1 allows attackers to execute arbitrary code via execParams.

Browse all CWE-862 (Missing Authorization) vulnerabilities →