# CVE-2024-10938: OVRI Payment 1.7.0 - Malicious .htaccess directive

> Malicious .htaccess directives in the OVRI Payment plugin allow attackers to bypass script execution restrictions or disrupt site functionality.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-4vr2-gvv5-x55w

## What is CVE-2024-10938?

CVE-2024-10938 is a medium-severity vulnerability in moneytigo OVRI Payment, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-506 (Embedded Malicious Code)

## Which versions are affected by CVE-2024-10938?


## How do I fix CVE-2024-10938?

No fix has been published for CVE-2024-10938 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10938 being exploited?

There is no known exploitation of CVE-2024-10938 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10938 and fix it if it is affected.

What it is: CVE-2024-10938 is a medium-severity vulnerability in moneytigo OVRI Payment, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10938 in the wild and no public exploit code.

Affected product: moneytigo OVRI Payment. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10938/ (Markdown: https://insights.sbomify.com/CVE-2024-10938/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10938
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10938
- OSV: https://osv.dev/vulnerability/CVE-2024-10938

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10938/
Summaries are generated and may contain mistakes; the official description above is the record.