TMS Amelia Plugin up to 1.0.95 on WordPress cross-site request forgery

Summaryinfo

A vulnerability identified as problematic has been detected in TMS Amelia Plugin up to 1.0.95 on WordPress. Affected by this issue is some unknown functionality. Performing a manipulation results in cross-site request forgery. This vulnerability is known as CVE-2024-31425. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in TMS Amelia Plugin up to 1.0.95 on WordPress. It has been classified as problematic. This affects some unknown functionality. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:

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

The weakness was published by Yudistira Arya. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2024-31425 since 04/03/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• TMS

Name

• Amelia Plugin

Version

• 1.0.0
• 1.0.1
• 1.0.2
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8
• 1.0.9
• 1.0.10
• 1.0.11
• 1.0.12
• 1.0.13
• 1.0.14
• 1.0.15
• 1.0.16
• 1.0.17
• 1.0.18
• 1.0.19
• 1.0.20
• 1.0.21
• 1.0.22
• 1.0.23
• 1.0.24
• 1.0.25
• 1.0.26
• 1.0.27
• 1.0.28
• 1.0.29
• 1.0.30
• 1.0.31
• 1.0.32
• 1.0.33
• 1.0.34
• 1.0.35
• 1.0.36
• 1.0.37
• 1.0.38
• 1.0.39
• 1.0.40
• 1.0.41
• 1.0.42
• 1.0.43
• 1.0.44
• 1.0.45
• 1.0.46
• 1.0.47
• 1.0.48
• 1.0.49
• 1.0.50
• 1.0.51
• 1.0.52
• 1.0.53
• 1.0.54
• 1.0.55
• 1.0.56
• 1.0.57
• 1.0.58
• 1.0.59
• 1.0.60
• 1.0.61
• 1.0.62
• 1.0.63
• 1.0.64
• 1.0.65
• 1.0.66
• 1.0.67
• 1.0.68
• 1.0.69
• 1.0.70
• 1.0.71
• 1.0.72
• 1.0.73
• 1.0.74
• 1.0.75
• 1.0.76
• 1.0.77
• 1.0.78
• 1.0.79
• 1.0.80
• 1.0.81
• 1.0.82
• 1.0.83
• 1.0.84
• 1.0.85
• 1.0.86
• 1.0.87
• 1.0.88
• 1.0.89
• 1.0.90
• 1.0.91
• 1.0.92
• 1.0.93
• 1.0.94
• 1.0.95

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion