Change Memory Limit

Vendor:

First CVE: Mar 5, 2024 · Active for 2 years

1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
5.3
Avg CVSS
Higher Avg CVSS than 10% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Change Memory Limit over time

Volume of CVEsAvg CVSS Base Score
First CVE
Mar 5, 2024
2 years ago
Most Recent CVE
Mar 5, 2024
872 days ago

CVE Severity & Scoring

Change Memory Limit1 CVEs
All CVEs352,708 CVEs
Medium
Attack Vector
Local0 (0.0%)
Network1 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None1 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None1 (100.0%)
Unknown0 (0.0%)

Top CVEs

Signals from CVEs in this product scope (1 CVEs).

1 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
The Change Memory Limit plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the admin_logic() function hooked via admin_ini
Mar 5, 20245.316NONO

Exploit Exposure

Signals from CVEs in this product scope (1 CVEs).

CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%

Social Chatter

Signals from CVEs in this product scope (1 CVEs).

Media Mentions

Signals from CVEs in this product scope (1 CVEs).

Top CNAs Publishing CVEs For Change Memory Limit

Top CWEs

Versions

VersionCVE CountAvg CVSSAvg EPSSKEVExploits
1.015.30.4%00