sbomify Insights

Search by CVE or GitHub advisory id, package name or title.

CVE-2024-0627 Custom Field Template <= 2.6.1 - Authenticated(Constibutor+) Stored Cross-Site Scripting via Custom Field Name

Medium 6.4 Published Updated

Authenticated attackers can inject arbitrary scripts via custom field names, leading to stored XSS execution for other users.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2024-0627?

CVE-2024-0627 is a medium-severity cross-site scripting vulnerability in hiroaki-miyashita Custom Field Template, published on 11 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's custom field name column in all versions up to, and including, 2.6.1 due to insufficient input sanitization and output escaping on user supplied custom fields. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Weakness: CWE-79

Which versions are affected by CVE-2024-0627?

It affects 1 product.

Products include Wpgogo Custom Field Template.

How do I fix CVE-2024-0627?

No fix has been published for CVE-2024-0627 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2024-0627 being exploited?

There is no known exploitation of CVE-2024-0627 in the wild and no public exploit code.

Sources

Also known as GHSA-prm3-v4r8-g2mv.

Is CVE-2024-0627 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free