CVE-2025-7688
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 Add User Meta plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the 'add-user-meta' page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 Add User Meta WordPress plugin versions up to 1.0.1 lacks proper nonce validation on the add-user-meta admin page, allowing unauthenticated attackers to forge requests that can modify plugin settings and inject malicious scripts by tricking administrators into clicking crafted links.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Locate Add User Meta plugin in WordPressNavigate to WordPress admin > Plugins > Installed Plugins and search for 'Add User Meta' in the plugin listAffected if The plugin is not found in the installed plugins list, indicating it is not installed and therefore not affected
-
Identify the installed version numberIn the Plugins list, locate the 'Add User Meta' plugin and read the version number displayed beneath the plugin name (e.g., 'Version 1.0.1')Affected if The plugin is installed and the version displays as 1.0.1 or any version lower than 1.0.1
-
Verify version against affected rangeCompare your installed version to the affected range: versions up to and including 1.0.1 are vulnerableAffected if Your version number is 1.0.1 or below, meaning the plugin lacks proper nonce validation and is affected by this CSRF vulnerability
If the Add User Meta plugin is installed with version 1.0.1 or lower, the environment is affected by CVE-2025-7688 due to missing nonce validation on the admin page.
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.
dbcve · scopedUpdate the plugin to the latest version when available and ensure admin users exercise caution with links to prevent CSRF attacks.
Latest available version of Add User Meta plugin (version higher than 1.0.1)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'Add User Meta' plugin
- 4. Check if an update is available for the plugin
- 5. If an update is available, click 'Update Now' to install the latest version
- 6. After updating, verify the plugin is functioning correctly
- 7. Consider using a security plugin or web application firewall as an interim mitigation if update is not available
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7688 — 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-7688 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