CVE-2020-26177

CVE-2020-26177 is a medium-severity vulnerability in Tangro Business Workflow with a CVSS 3.x base score of 4.3. 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-669.

Key facts

Description

In tangro Business Workflow before 1.18.1, a user's profile contains some items that are greyed out and thus are not intended to be edited by regular users. However, this restriction is only applied client-side. Manipulating any of the greyed-out values in requests to /api/profile is not prohibited server-side.

Frequently asked questions

What is CVE-2020-26177?
In tangro Business Workflow before 1.18.1, a user's profile contains some items that are greyed out and thus are not intended to be edited by regular users. However, this restriction is only applied client-side. Manipulating any of the greyed-out values in requests to /api/profile is not prohibited server-side.
How severe is CVE-2020-26177?
CVE-2020-26177 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2020-26177 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (46th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-26177?
CVE-2020-26177 affects Tangro Business Workflow. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-26177?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-26177 published?
CVE-2020-26177 was published on 2020-12-18 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Tangro Business Workflow

All CVEs affecting Tangro Business Workflow →

Other CWE-669 vulnerabilities

Browse all CWE-669 vulnerabilities →