Public Knowledge Project omp/ojs Payment Instructions Setting paymentForm.tpl cross site scripting

The XSS vulnerability in OMP allows an attacker to inject arbitrary JavaScript code into the web page viewed by other users. This can be exploited to steal user credentials, redirect users to malicious websites, or deface the website. The impact is particularly severe if the OMP instance is used to manage sensitive data or handle financial transactions. An attacker could potentially gain unauthorized access to user accounts and perform actions on their behalf. While the CVSS score is LOW, the potential for user data compromise and website manipulation warrants immediate attention.

Organizations and individuals using Public Knowledge Project OMP for publishing monographs and other scholarly works are at risk. This includes academic institutions, research organizations, and publishers who rely on OMP for their content management needs. Shared hosting environments where multiple OMP instances are hosted on the same server are particularly vulnerable, as a compromise of one instance could potentially affect others.

• php: Examine the plugins/paymethod/manual/templates/paymentForm.tpl file for unsanitized input handling of the manualInstructions variable. Search for instances where this variable is directly output to the page without proper encoding.

// Example of vulnerable code
echo $_GET['manualInstructions'];

• generic web: Monitor access logs for unusual requests targeting the plugins/paymethod/manual/templates/paymentForm.tpl endpoint with potentially malicious parameters in the manualInstructions query string. Use a WAF to block requests containing suspicious JavaScript code.

grep "<script" /var/log/apache2/access.log

1. 2025-11-20Disclosure

   disclosure

1. 已保留2025-11-20
2. 发布日期2025-11-20
3. EPSS 更新日期2026-03-23

The primary mitigation for CVE-2025-13469 is to upgrade to OMP version 3.5.1 or later, which contains the fix. If upgrading is not immediately feasible, consider implementing input validation and sanitization on the manualInstructions parameter to prevent malicious code from being injected. Web Application Firewalls (WAFs) configured to detect and block XSS attacks can also provide an additional layer of protection. Review and update any custom plugins or themes to ensure they do not introduce similar vulnerabilities.