Strategic Overview
- Status
- Unpatched
- Affected Plugin
- OVRI Payment
- Affected Version
1.7.0- CVSS
- 6.5Medium
- Weakness type
- CWE-506 · Embedded Malicious Code
- CVE
CVE-2024-10938
At a glance
CVE-2024-10938 is a medium-severity Embedded Malicious Code vulnerability in the OVRI Payment WordPress plugin, affecting versions 1.7.0. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed February 2026, reported by Marco Wotschka.
Vulnerability Overview
The OVRI Payment plugin for WordPress contains malicious .htaccess files in version 1.7.0. The files contain directives to prevent the execution of certain scripts while allowing execution of known malicious PHP files. If moved outside of the plugin's directory, they may interfere with the proper function of a site.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-506: Embedded Malicious Code
Reaching this weakness in OVRI Payment 1.7.0 takes a caller who can reach the endpoint. Embedded malicious code means functionality was deliberately placed in the software to act against the site owner's interest, rather than being an accidental defect.
Removing the software is not enough on its own — anything it created or modified while active has to be audited too. No fixed build of this plugin is recorded for OVRI Payment yet, so installs running 1.7.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C