Wp Tell A Friend Popup FormWordPress extension · Gopiplus
CVE-2023-25463
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Gopi Ramasamy WP tell a friend popup form plugin <= 7.1 versions.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP tell a friend popup form plugin for WordPress (versions <= 7.1). The plugin fails to properly validate anti-CSRF tokens, allowing attackers to trick authenticated users into performing unintended actions via malicious requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Tell A Friend Popup FormWordPress extension
<= 7.1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Identify if the plugin is installedCheck your WordPress installation's wp-content/plugins directory for a folder named 'wp-tell-a-friend-popup-form' or 'gopi-wp-tell-a-friend-popup-form', or list installed plugins via wp-admin > Plugins.Affected if The plugin folder exists in the plugins directory.
-
Determine the installed versionIf the plugin folder exists, look inside for a readme.txt or main PHP file containing 'Version:' metadata, or check the plugin entry in wp-admin > Plugins.Affected if The reported version is 7.1 or lower.
-
Locate form handling codeIn the plugin folder, identify PHP files that handle form submissions (typically files with 'submit', 'post', 'form', or 'ajax' in the name, or the main plugin entry point file).Affected if Form handling PHP files exist in the plugin.
-
Inspect for missing nonce validationOpen the form handling PHP files and search for 'wp_verify_nonce', 'check_admin_referer', or 'wp_create_nonce'. Check if these nonce verification functions are present BEFORE any state-changing operations (sending emails, saving data, etc.).Affected if No nonce verification functions are found in form processing code, or verification occurs AFTER the action is processed.
You are affected if the Gopiplus Wp Tell A Friend Popup Form plugin is installed with version 7.1 or lower AND its form handling code lacks wp_verify_nonce or check_admin_referer calls before processing submissions.
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 dataImplement WordPress nonces (wp_create_nonce/wp_verify_nonce) in all form submissions and AJAX handlers within the plugin, and verify nonce validation before processing any state-changing requests.
Fix this in Wp Tell A Friend Popup Form
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25463 — 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-2023-25463 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