Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-5549: A CORS misconfiguration in the stitionai/devika repository allows attackers to steal sensitive information suc

39
Routine
HIGH 8.1DOWNGRADE

CVE-2024-5549 is a high-severity flaw (CVSS 8.1) affecting devika. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A CORS misconfiguration in the stitionai/devika repository allows attackers to steal sensitive information such as logs, browser sessions, and settings containing private API keys from other services. This vulnerability also enables attackers to perform actions on behalf of the user, such as deleting projects or sending messages. The issue arises from the lack of proper origin validation, allowing unauthorized cross-origin requests to be executed

Why this priority

  • High severity
  • Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.3% (top 78%)
CISA exploited listNo
WeaknessCWE-346
Published2024-07-09
Last modified2026-06-17
Publisher (CNA): huntr.dev · Vendor: stitionai

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

stitionai devika DOWNGRADE
Affected: 1.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0
1. Check installed version
apt-cache policy devika || rpm -q devika || devika --version
2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)
apt-cache madison devika sudo apt install devika=<VERSION_BEFORE_1.0> sudo apt-mark hold devika
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list devika sudo dnf downgrade devika-<VERSION_BEFORE_1.0> sudo dnf versionlock add devika
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-5549?

devika: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-5549 being exploited?

CVE-2024-5549 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-5549 affect?

CVE-2024-5549 affects devika. Severity is high (CVSS 8.1). A CORS misconfiguration in the stitionai/devika repository allows attackers to steal sensitive information such as logs, browser sessions, and settings containing private API keys from other services. This vulnerability also enables attacke

How urgent is CVE-2024-5549?

Priority 39/100. High severity; Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.