# CVE-2025-14608: WP Last Modified Info <= 1.9.5 - Insecure Direct Object Reference to Authenticated (Author+) Post Metadata Modification

> Authenticated attackers with Author access can modify metadata of arbitrary posts, including those by Administrators, due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-mx27-m68w-fph6

## What is CVE-2025-14608?

CVE-2025-14608 is a medium-severity missing authorization vulnerability in infosatech WP Last Modified Info, published on 14 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Last Modified Info plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.9.5. This is due to the plugin not validating a user's access to a post before modifying its metadata in the 'bulk_save' AJAX action. This makes it possible for authenticated attackers, with Author-level access and above, to update the last modified metadata and lock the modification date of arbitrary posts, including those created by Administrators via the 'post_ids' parameter.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-14608?


## How do I fix CVE-2025-14608?

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

## Is CVE-2025-14608 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14608 and fix it if it is affected.

What it is: CVE-2025-14608 is a medium-severity missing authorization vulnerability in infosatech WP Last Modified Info, published on 14 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-2025-14608 in the wild and no public exploit code.

Affected product: infosatech WP Last Modified Info. 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-2025-14608/ (Markdown: https://insights.sbomify.com/CVE-2025-14608/index.md)
```

## Sources

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

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