CVE-2025-48233
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 affmngr Affiliates Manager Google reCAPTCHA Integration affiliates-manager-google-recaptcha-integration allows Stored XSS.This issue affects Affiliates Manager Google reCAPTCHA Integration: from n/a through <= 1.0.6.
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 confidenceCSRF vulnerability in the Affiliates Manager Google reCAPTCHA Integration plugin (versions <= 1.0.6) allows authenticated attackers to inject Stored XSS by tricking administrators into submitting malicious requests. The attack chain uses CSRF to bypass authentication and store malicious scripts that execute when other users view the affected admin interface areas.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Verify plugin installation and versionAccess WordPress admin dashboard, navigate to Plugins section, locate 'Affiliates Manager Google reCAPTCHA Integration', and record the installed version number. Alternatively, inspect the plugin main file header for the Version field.Affected if The plugin is installed with version 1.0.6 or lower.
-
Confirm admin form CSRF protection existsExamine the plugin source code for WordPress nonce verification functions such as wp_nonce_field, wp_verify_nonce, or check_admin_referer on all admin-facing form submissions and URL parameters.Affected if No nonce verification is found on admin forms that handle reCAPTCHA settings or other stored configuration data.
-
Inspect stored data output sanitizationReview plugin code where stored data is retrieved and displayed in admin interface areas. Look for sanitization functions like esc_html, esc_attr, or sanitize_text_field when outputting stored values.Affected if Stored plugin configuration or user-supplied data is output in admin areas without proper sanitization.
-
Identify affected admin interface areasDetermine which admin pages or settings panels use the Google reCAPTCHA integration feature. These are the areas where malicious scripts could be stored and later executed.Affected if The plugin provides admin pages where reCAPTCHA settings or related data can be saved and viewed by other administrators.
If the plugin is installed with version 1.0.6 or lower and admin forms lack CSRF nonce protection, the environment is vulnerable to stored XSS via CSRF.
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 dataApply vendor patch when available. Until then, disable the plugin or restrict admin access, implement anti-CSRF tokens (nonces) on all admin forms, and ensure all stored data is properly sanitized before output.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48233 — 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-48233 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