CVE-2025-48077
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 nitinmaurya12 Block Country block-country allows Stored XSS.This issue affects Block Country: from n/a through <= 1.0.
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 confidenceA CSRF vulnerability in the Block Country WordPress plugin allows attackers to trick authenticated administrators into submitting malicious requests that result in stored XSS. The lack of anti-CSRF tokens on forms enables attackers to inject malicious scripts that persist in the database and execute in admin browsers.
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 Block Country plugin is installedNavigate to WordPress admin > Plugins and confirm Block Country is active, or inspect wp-content/plugins/ directory for the block-country folderAffected if Block Country plugin is installed and active
-
Determine plugin versionCheck the plugin header in block-country/block-country.php for the Version field, or view the plugin details in WordPress admin Plugins listAffected if Installed version matches any vulnerable version of this plugin (no specific version range provided)
-
Inspect plugin PHP files for nonce implementationSearch plugin PHP files (particularly form handlers in block-country.php or admin/*.php) for presence of wp_nonce_field, wp_verify_nonce, or check_admin_referer calls on state-changing formsAffected if Forms processing country block settings lack nonce verification (vulnerable code missing these function calls)
-
Check for input sanitization on stored dataExamine PHP files where user input (country codes, settings) is saved to the database - look for sanitize_text_field, esc_attr, or similar sanitization functions before update_option or insert statementsAffected if User-supplied country blocking data is saved without proper sanitization functions
-
Verify output encoding when displaying stored dataReview admin dashboard code that reads and displays blocked countries - confirm esc_html or esc_attr is used when outputting stored values in HTML contextAffected if Stored country data is echoed in admin pages without escaping functions, allowing script injection to persist and execute
A user is affected if the Block Country plugin is installed and its admin forms handling country blocking lack nonce verification combined with insufficient sanitization/encoding of stored input.
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 nonces/tokens on all state-changing forms to prevent CSRF attacks, and apply proper input sanitization plus output encoding when displaying any user-controlled data to prevent stored XSS.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48077 — 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-48077 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