Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.1%top 68%

CVE-2024-31425: CWE-352 Cross-Site Request Forgery (CSRF) in TMS Amelia

0
Medium
VulnerabilityCVE-2024-31425cvecve-2024-31425cwe-352
Published: Mon Apr 15 2024 (04/15/2024, 10:05:45 UTC)
Source: CVE Database V5
Vendor/Project: TMS
Product: Amelia

Description

Cross-Site Request Forgery (CSRF) vulnerability in TMS Amelia.This issue affects Amelia: from n/a through 1.0.95.

CVSS v3.1

Score 5.4medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Affected software

Affected versions
<=1.0.95

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/29/2026, 09:37:31 UTC

Technical Analysis

This vulnerability, identified as CWE-352, exists in TMS Amelia versions up to 1.0.95 and involves Cross-Site Request Forgery (CSRF). CSRF vulnerabilities enable attackers to trick authenticated users into submitting unauthorized requests to the web application, potentially causing unintended actions. The CVSS 3.1 vector indicates the attack can be performed remotely without privileges, requires user interaction, and impacts integrity and availability with no confidentiality impact. No patch or official remediation level has been disclosed by the vendor, and no exploits are known in the wild.

Potential Impact

The impact of this vulnerability is limited to potential unauthorized actions performed on behalf of authenticated users, affecting the integrity and availability of the application. There is no confidentiality impact reported. Since no known exploits are in the wild, the immediate risk is moderate but could increase if exploitation techniques emerge.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing standard CSRF mitigations such as verifying the origin of requests, using anti-CSRF tokens, or restricting sensitive actions to POST requests with proper validation. Monitor vendor communications for updates on patches or official mitigations.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2024-04-03T12:22:47.292Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69f1651bcbff5d86104aa2af

Added to database: 4/29/2026, 1:55:39 AM

Last enriched: 4/29/2026, 9:37:31 AM

Last updated: 6/13/2026, 12:02:41 PM

Views: 36

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses