What is CVE-2025-13158?

CVE-2025-13158 is a critical-severity security vulnerability in apidoc-core (npm), affecting versions >= 0.2.0, <= 0.15.0. No fixed version is listed yet.

Which versions of apidoc-core are affected by CVE-2025-13158?

apidoc-core (npm) versions >= 0.2.0, <= 0.15.0 is affected.

Is there a fix for CVE-2025-13158?

No fixed version is listed for CVE-2025-13158 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2025-13158 exploitable, and should I be worried?

Whether CVE-2025-13158 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-2025-13158 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.

CVE-2025-13158 in apidoc-core | Intelligent Application Security

Q: Which versions of apidoc-core are affected by CVE-2025-13158?

apidoc-core (npm) versions >= 0.2.0, <= 0.15.0 is affected.

Q: Is there a fix for CVE-2025-13158?

No fixed version is listed for CVE-2025-13158 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2025-13158 exploitable, and should I be worried?

Whether CVE-2025-13158 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-2025-13158 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.

Summary

Prototype pollution vulnerability in apidoc-core versions 0.2.0 and all subsequent versions allows remote attackers to modify JavaScript object prototypes via malformed data structures, including the “define” property processed by the application, potentially leading to denial of service or unintended behavior in applications relying on the integrity of prototype chains. This affects the preProcess() function in api_group.js, api_param_title.js, api_use.js, and api_permission.js worker modules.

Impact

Affected versions

apidoc-core (>= 0.2.0, <= 0.15.0)

Security releases

Not available

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.

See it in your environment

Remediation advice

No fixed version is listed for CVE-2025-13158 yet.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-13158? CVE-2025-13158 is a critical-severity security vulnerability in apidoc-core (npm), affecting versions >= 0.2.0, <= 0.15.0. No fixed version is listed yet.
Which versions of apidoc-core are affected by CVE-2025-13158? apidoc-core (npm) versions >= 0.2.0, <= 0.15.0 is affected.
Is there a fix for CVE-2025-13158? No fixed version is listed for CVE-2025-13158 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2025-13158 exploitable, and should I be worried? Whether CVE-2025-13158 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-2025-13158 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.

Other vulnerabilities in apidoc-core

CVE-2025-13158