What is CVE-2024-56510?

CVE-2024-56510 is a medium-severity cross-site scripting (XSS) vulnerability in @marp-team/marp-core (npm), affecting versions >= 3.0.2, <= 3.9.0. It is fixed in 3.9.1, 4.0.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2024-56510?

CVE-2024-56510 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @marp-team/marp-core are affected by CVE-2024-56510?

@marp-team/marp-core (npm) versions >= 3.0.2, <= 3.9.0 is affected.

Is there a fix for CVE-2024-56510?

Yes. CVE-2024-56510 is fixed in 3.9.1, 4.0.1. Upgrade to this version or later.

Is CVE-2024-56510 exploitable, and should I be worried?

Whether CVE-2024-56510 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-56510 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-56510?

Upgrade: @marp-team/marp-core to 3.9.1 or later, @marp-team/marp-core to 4.0.1 or later.

CVE-2024-56510 in @marp-team/marp-core

Q: How severe is CVE-2024-56510?

CVE-2024-56510 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @marp-team/marp-core are affected by CVE-2024-56510?

@marp-team/marp-core (npm) versions >= 3.0.2, <= 3.9.0 is affected.

Q: Is there a fix for CVE-2024-56510?

Yes. CVE-2024-56510 is fixed in 3.9.1, 4.0.1. Upgrade to this version or later.

Q: Is CVE-2024-56510 exploitable, and should I be worried?

Whether CVE-2024-56510 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-56510 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-56510?

Upgrade: @marp-team/marp-core to 3.9.1 or later, @marp-team/marp-core to 4.0.1 or later.

Summary

Marp Core allows XSS by improper neutralization of HTML sanitization

Marp Core (@marp-team/marp-core) from v3.0.2 to v3.9.0 and v4.0.0, are vulnerable to cross-site scripting (XSS) due to improper neutralization of HTML sanitization.

Workarounds

If you are unable to update the package immediately, disable all HTML tags by setting html: false option in the Marp class constructor.

const marp = new Marp({ html: false })

References

Credits

Thanks to @Ry0taK for finding out this vulnerability.

Impact

Marp Core includes an HTML sanitizer with allowlist support. In the affected versions, the built-in allowlist is enabled by default. When the allowlist is active, if insufficient HTML comments are included, the sanitizer may fail to properly sanitize HTML content and lead cross-site scripting (XSS).

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-56510 has a CVSS score of 5.3 (Medium). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.9.1, 4.0.1); upgrading removes the vulnerable code path.

Affected versions

@marp-team/marp-core (>= 3.0.2, <= 3.9.0) @marp-team/marp-core (= 4.0.0)

Security releases

@marp-team/marp-core → 3.9.1 (npm) @marp-team/marp-core → 4.0.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Marp Core v3.9.1 and v4.0.1 have been patched to fix that.

Frequently Asked Questions

What is CVE-2024-56510? CVE-2024-56510 is a medium-severity cross-site scripting (XSS) vulnerability in @marp-team/marp-core (npm), affecting versions >= 3.0.2, <= 3.9.0. It is fixed in 3.9.1, 4.0.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2024-56510? CVE-2024-56510 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @marp-team/marp-core are affected by CVE-2024-56510? @marp-team/marp-core (npm) versions >= 3.0.2, <= 3.9.0 is affected.
Is there a fix for CVE-2024-56510? Yes. CVE-2024-56510 is fixed in 3.9.1, 4.0.1. Upgrade to this version or later.
Is CVE-2024-56510 exploitable, and should I be worried? Whether CVE-2024-56510 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-56510 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-56510?
- Upgrade @marp-team/marp-core to 3.9.1 or later
- Upgrade @marp-team/marp-core to 4.0.1 or later