NVD / CVE Program· CNA GitHub_M

CVE-2024-39319: aimeos/ai-controller-frontend has IDOR vulnerability in account profile page

Noroxi assessment

Priority: Monitor (action score 21/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: 0.48% (FIRST EPSS).
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 CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: aimeos/ai-controller-frontend (Packagist) 2021.10.8, 2022.10.8, 2023.10.9.

Low priority for now. Upgrade to aimeos/ai-controller-frontend (Packagist) 2021.10.8, 2022.10.8, 2023.10.9 or later.

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

aimeos/ai-controller-frontend is the Aimeos frontend controller package for e-commerce projects. Prior to versions 2024.4.2, 2023.10.9, 2022.10.8, 2021.10.8, and 2020.10.15, an insecure direct object reference allows an attacker to disable subscriptions and reviews of another customer. Versions 2024.4.2, 2023.10.9, 2022.10.8, 2021.10.8, and 2020.10.15 fix this issue.

MediumCVSS 5.3 · v3.1—No exploit Fix available

GHSA-rw3j-574h-mrcq

Published: Sep 26, 2024
Updated: Jun 17, 2026
EPSS: 0.4% · 42th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 5.3
CNA · GitHub_M: 5.3; agree

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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
A fix has been released

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

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
aimeos	aimeos frontend controller	cpe:2.3:a:aimeos:aimeos_frontend_controller

Affected versions

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

aimeos aimeos frontend controllerbefore 2020.10.15
aimeos aimeos frontend controller2021.04.1 and later · before 2021.10.8
aimeos aimeos frontend controller2022.04.1 and later · before 2022.10.8
aimeos aimeos frontend controller2023.04.1 and later · before 2023.10.9
aimeos aimeos frontend controller2024.04.1

Versions reported by the vendor

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

aimeos ai-controller-frontend
- = 2024.04.1, >= 2023.04.1, < 2023.10.9, >= 2022.04.1, < 2022.10.8, >= 2021.04.1, < 2021.10.8, < 2020.10.15affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Packagist	aimeos/ai-controller-frontend	from 2021.04.1 · before 2021.10.8	2021.10.8
Packagist	aimeos/ai-controller-frontend	from 2022.04.1 · before 2022.10.8	2022.10.8
Packagist	aimeos/ai-controller-frontend	from 2023.04.1 · before 2023.10.9	2023.10.9
Packagist	aimeos/ai-controller-frontend	from 2024.04.1 · before 2024.04.2	2024.04.2
Packagist	aimeos/ai-controller-frontend	before 2020.10.15	2020.10.15

Same product

aimeos: all records

Other highest-scoring records for the same primary product.

CVE-2024-39325aimeos/ai-controller-frontend doesn't reset payment status in basket
21Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Packagist:aimeos/ai-controller-frontend	2020.10.15	Package registry (OSV)
Packagist:aimeos/ai-controller-frontend	2021.10.8	Package registry (OSV)
Packagist:aimeos/ai-controller-frontend	2022.10.8	Package registry (OSV)
Packagist:aimeos/ai-controller-frontend	2023.10.9	Package registry (OSV)
Packagist:aimeos/ai-controller-frontend	2024.04.2	Package registry (OSV)

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.

Credits

All researchers

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

No credits in the CNA record.

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).

Technical details

Attack conditions

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.

If successful

Confidentiality: none
Integrity: low · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: Low
Availability impact: None

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

nvd-primary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/aimeos/ai-controller-frontend/commit/2ad5c062a629af374da470a319914c321c9bfee2

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records