CVE-2020-26527

CVE-2020-26527 is a critical-severity vulnerability in Damstratechnology Smart Asset with a CVSS 3.x base score of 9.8. 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-346.

Key facts

Description

An issue was discovered in API/api/Version in Damstra Smart Asset 2020.7. Cross-origin resource sharing trusts random origins by accepting the arbitrary 'Origin: example.com' header and responding with 200 OK and a wildcard 'Access-Control-Allow-Origin: *' header.

Frequently asked questions

What is CVE-2020-26527?
An issue was discovered in API/api/Version in Damstra Smart Asset 2020.7. Cross-origin resource sharing trusts random origins by accepting the arbitrary 'Origin: example.com' header and responding with 200 OK and a wildcard 'Access-Control-Allow-Origin: *' header.
How severe is CVE-2020-26527?
CVE-2020-26527 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-26527 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (56th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-26527?
CVE-2020-26527 affects Damstratechnology Smart Asset. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-26527?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2020-26527 published?
CVE-2020-26527 was published on 2020-10-02 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Damstratechnology Smart Asset

All CVEs affecting Damstratechnology Smart Asset →

Other CWE-346 vulnerabilities

Browse all CWE-346 vulnerabilities →