Wp Page NumbersWordPress extension · Jenst
CVE-2023-27623
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 Jens Törnell WP Page Numbers plugin <= 0.5 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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Page Numbers WordPress plugin versions 0.5 and below allows attackers to trick authenticated administrators into performing unintended actions (such as modifying plugin settings) by forging HTTP 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 Page NumbersWordPress extension
<= 0.5CVSS 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.
-
Confirm WP Page Numbers plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'WP Page Numbers' or 'Jenst Wp Page Numbers'. Note the version displayed.Affected if The plugin is installed and the version shown is 0.5 or lower.
-
Verify plugin version numberIn the plugins list, locate the version number column for WP Page Numbers plugin. Compare it to the affected version range of 0.5 and below.Affected if The installed version is 0.5 or any version number lower than 0.5.
-
Inspect plugin admin forms for nonce fieldsNavigate to the plugin settings page (usually under Settings > Page Numbers). View the page source (right-click > View Page Source) and search for 'wp_nonce' or '_wpnonce' in the form HTML.Affected if The plugin settings forms do NOT contain any WordPress nonce fields (wp_nonce_field, _wpnonce) in the HTML source.
-
Check plugin AJAX handlers for nonce verificationLocate the plugin PHP files (typically in wp-content/plugins/wp-page-numbers/). Search the codebase for AJAX action handlers (add_action with 'wp_ajax_') and check if they verify nonces using check_ajax_referer or wp_verify_nonce.Affected if The plugin AJAX endpoints exist but do not call check_ajax_referer or wp_verify_nonce to validate request origin.
You are affected if the WP Page Numbers plugin is installed with version 0.5 or below, and its admin forms and AJAX endpoints lack WordPress 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 dataImplement WordPress nonces (anti-CSRF tokens) on all state-changing forms and AJAX endpoints within the plugin to verify request origin and intent.
Fix this in Wp Page Numbers
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27623 — 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-27623 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