NVD / CVE Program· CNA INCIBE

CVE-2021-3833: Integria IMS incorrect authorization

Noroxi assessment

Priority: Monitor (action score 39/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: 1.1% (FIRST EPSS); higher than 66.1% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

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

Integria IMS login check uses a loose comparator ("==") to compare the MD5 hash of the password provided by the user and the MD5 hash stored in the database. An attacker with a specific formatted password could exploit this vulnerability in order to login in the system with different passwords.

CriticalCVSS 9.8 · v3.1—No exploit No fix recorded

Pre-auth

Published: Oct 7, 2021
Updated: Jun 17, 2026
EPSS: 1.1% · 66th percentile
CWE: CWE-697

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.1%

CNA vs NVD score

NVD: 9.8
CNA · INCIBE: 9.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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
artica	integria ims	cpe:2.3:a:artica:integria_ims

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

artica integria ims5.0.92

Versions reported by the vendor

Affected version ranges reported by the assigning authority (INCIBE). Independent of NVD's CPE analysis and usually ahead of it.

Ártica Integria IMS
- 5.0.92affected

Same product

artica: all records

Other highest-scoring records for the same primary product.

CVE-2021-3832Integria IMS Remote Code Execution
40Plan
CVE-2019-15091filemgr.php in Artica Integria IMS 5.0.86 allows index.php?sec=wiki&sec2=operation/wiki/wiki&action=upload arbitrary file upload.
39Monitor
CVE-2018-1000812Artica Integria IMS version 5.0 MR56 Package 58, likely earlier versions contains a CWE-640: Weak Password Recovery Mechanism for Forgotten
33Monitor

Published before and after this one in the same product

← EarlierCVE-2018-19828Dec 17, 2018 · Artica Integria IMS 5.0.83 has XSS via the search_string parameter.
25Monitor
← EarlierCVE-2018-19829Dec 18, 2018 · Artica Integria IMS 5.0.83 has CSRF in godmode/usuarios/lista_usuarios, resulting in the ability to delete an arbitrary user when the ID num
27Monitor
Later →CVE-2021-3834Oct 7, 2021 · Integria IMS vulnerable to Cross Site Scripting (XSS)
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

@nag0mez (special mention to @_Barriuso)finder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).