# CVE-2025-7664: Missing authorization in AL Pack

> Unauthenticated attackers can activate premium features by spoofing the Origin header due to missing authorization checks in the AL Pack WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 16 Aug 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2vwh-54r8-6xwg

## What is CVE-2025-7664?

CVE-2025-7664 is a high-severity missing authorization vulnerability in loword AL Pack, published on 16 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AL Pack plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the check_activate_permission() permission callback for the /wp-json/presslearn/v1/activate REST API endpoint in all versions up to, and including, 1.1.1. The callback reads the client-supplied Origin header and, after parsing, allows the request if it matches one of the trusted domains, without ever verifying user authentication, capabilities, or nonce tokens. This makes it possible for unauthenticated attackers to activate premium features by simply spoofing the Origin header.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-7664 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7664 is a high-severity missing authorization vulnerability in loword AL Pack, published on 16 Aug 2025. 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-7664 in the wild and no public exploit code.

Affected product: loword AL Pack. 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-7664/ (Markdown: https://insights.sbomify.com/CVE-2025-7664/index.md)
```

## Sources

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

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