What is CVE-2025-53625?

CVE-2025-53625 is a high-severity security vulnerability in universal-omega/dynamic-page-list3 (composer), affecting versions < 3.6.4. It is fixed in 3.6.4.

Which versions of universal-omega/dynamic-page-list3 are affected by CVE-2025-53625?

universal-omega/dynamic-page-list3 (composer) versions < 3.6.4 is affected.

Is there a fix for CVE-2025-53625?

Yes. CVE-2025-53625 is fixed in 3.6.4. Upgrade to this version or later.

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

Whether CVE-2025-53625 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-53625 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-53625 in universal-omega/dynamic-page-list3

Q: Which versions of universal-omega/dynamic-page-list3 are affected by CVE-2025-53625?

universal-omega/dynamic-page-list3 (composer) versions < 3.6.4 is affected.

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

Yes. CVE-2025-53625 is fixed in 3.6.4. Upgrade to this version or later.

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

Whether CVE-2025-53625 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-53625 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-2025-53625?

Upgrade universal-omega/dynamic-page-list3 to 3.6.4 or later.

Summary

DynamicPageList3 vulnerability exposes hidden/suppressed usernames

Several #dpl parameters can leak usernames that have been hidden using revision deletion, suppression, or the hideuser block flag.

Details

The parameters adduser, addauthor, and addlasteditor output the page creator or last editor using the %USER% placeholder. These display the actual username, even when that name has been hidden using revision deletion, suppression (oversight), or hideuser.

The %CONTRIBUTOR% placeholder, used with addcontribution, behaves similarly and also reveals hidden usernames.

In addition, the following parameters can expose suppressed usernames when combined with %USER% or similar output placeholders:

lastrevisionbefore
allrevisionsbefore
firstrevisionsince
allrevisionssince

These parameters reference specific revisions and allow output of user-related metadata. If a username has been hidden from those revisions, it may still appear in the output.

Further, the parameters createdby, notcreatedby, modifiedby, notmodifiedby, lastmodifiedby, and notlastmodifiedby accept usernames as input. When the correct (suppressed) username is used, the query may return matching pages or edits. This can reveal the presence and association of a hidden identity, even if not displayed directly. However, this is a more indirect exposure than the output parameters mentioned above.

Proof of Concept

Create a page while logged in as a user.
Revision delete or suppress the username from the page history.
Use a DPL query with one of the affected parameters.
The output reveals the hidden username.

Example

The following query reveals the suppressed username Example user:

{{#dpl:
| title = File:Example.png
| addauthor = true
| format = ,%USER%,,
}}

Similar behavior occurs using parameters like lastrevisionbefore with %USER% in the format string.

Impact

This issue causes the exposure of usernames that were intentionally hidden by administrators. It directly undermines revision deletion, user suppression, and block-related privacy measures. In some cases, usernames can be revealed both directly through output and indirectly through query behavior.

Affected versions

universal-omega/dynamic-page-list3 (< 3.6.4)

Security releases

universal-omega/dynamic-page-list3 → 3.6.4 (composer)

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

Upgrade universal-omega/dynamic-page-list3 to 3.6.4 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is CVE-2025-53625? CVE-2025-53625 is a high-severity security vulnerability in universal-omega/dynamic-page-list3 (composer), affecting versions < 3.6.4. It is fixed in 3.6.4.
Which versions of universal-omega/dynamic-page-list3 are affected by CVE-2025-53625? universal-omega/dynamic-page-list3 (composer) versions < 3.6.4 is affected.
Is there a fix for CVE-2025-53625? Yes. CVE-2025-53625 is fixed in 3.6.4. Upgrade to this version or later.
Is CVE-2025-53625 exploitable, and should I be worried? Whether CVE-2025-53625 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-53625 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-2025-53625? Upgrade universal-omega/dynamic-page-list3 to 3.6.4 or later.