CVE-2025-7664
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe AL Pack WordPress plugin has a broken access control vulnerability in its REST API endpoint /wp-json/presslearn/v1/activate. The permission callback only validates the client-supplied Origin header against a whitelist but never verifies user authentication, capabilities, or nonce tokens, allowing unauthenticated attackers to activate premium features by spoofing the Origin header.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm AL Pack plugin is installedNavigate to WordPress admin > Plugins and look for 'AL Pack' in the installed plugins list, or check the /wp-content/plugins/ directory for an 'al-pack' folderAffected if AL Pack plugin is present in the WordPress installation
-
Check AL Pack installed versionIn WordPress admin > Plugins, find AL Pack and note the version number displayed, or read the version from the plugin's main PHP file header in /wp-content/plugins/al-pack/Affected if The installed version has not been patched and falls within the vulnerable range
-
Verify vulnerable REST API endpoint existsSend a GET request to /wp-json/presslearn/v1/activate and check if the endpoint responds (even with an error). Use: curl -s -o /dev/null -w '%{http_code}' https://yourdomain.com/wp-json/presslearn/v1/activateAffected if The endpoint returns any HTTP response (indicating the route is registered and active)
-
Test endpoint access control behaviorSend a request to the endpoint with a spoofed Origin header matching a whitelisted domain. Example: curl -H 'Origin: https://example.com' -X POST https://yourdomain.com/wp-json/presslearn/v1/activate -d '{}' -w '\n%{http_code}'Affected if The endpoint accepts the request without requiring authentication (no 401/403 response indicating auth failure)
A user is affected if the AL Pack plugin is installed with a vulnerable version and the /wp-json/presslearn/v1/activate endpoint is accessible without requiring valid user authentication or nonce verification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the AL Pack plugin to the latest patched version once available, or remove/disable the plugin if no patch exists. As a temporary mitigation, consider blocking access to the affected REST API endpoint at the web server level.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data