Most And Least Read Posts WidgetWordPress extension · Whiletrue
CVE-2024-49628
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 whiletrue Most And Least Read Posts Widget most-and-least-read-posts-widget allows Cross Site Request Forgery.This issue affects Most And Least Read Posts Widget: from n/a through <= 2.5.18.
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 'Most And Least Read Posts Widget' WordPress plugin (versions up to and including 2.5.18). Attackers can trick authenticated administrators into unknowingly submitting malicious requests to the plugin's admin actions, potentially allowing unauthorized configuration changes or data manipulation.
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
Most And Least Read Posts WidgetWordPress extension
< 2.5.19CVSS 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.
-
Locate the plugin installationCheck if the 'Most And Least Read Posts Widget' plugin is installed in your WordPress environment. This is typically found in the wp-content/plugins/ directory.Affected if The plugin directory 'most-and-least-read-posts-widget' or similar exists on the server.
-
Determine the installed plugin versionOpen the main plugin file (usually the primary PHP file in the plugin directory) and locate the version header comment, or check the plugin's readme.txt file for the 'Stable tag' version number.Affected if The reported version is less than 2.5.19 (for example, 2.5.18, 2.5.17, etc.).
-
Access the WordPress admin plugin listLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Find 'Most And Least Read Posts Widget' and note the version displayed.Affected if The version shown in the plugin list is 2.5.18 or lower.
-
Inspect admin action handlers for nonce verificationExamine the plugin's PHP files that handle admin POST/GET requests (typically files containing form processing or settings updates). Look for the presence of wp_verify_nonce or check_admin_referer calls before processing state-changing operations.Affected if State-changing admin actions (such as saving settings or modifying plugin configuration) lack nonce verification logic.
You are affected if the plugin is installed and the installed version is 2.5.18 or lower, or if admin actions in the plugin code lack proper nonce validation for CSRF protection.
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 · scoped2.5.19
Implement WordPress nonces (anti-CSRF tokens) on all state-changing admin actions and forms within the plugin, and verify these nonces on POST/GET handler functions.
2.5.19
- 1. Back up your WordPress site before making any changes
- 2. Navigate to Dashboard > Plugins in your WordPress admin
- 3. Find the 'Most And Least Read Posts Widget' plugin in your installed plugins list
- 4. If an update is available, click 'Update Now' to upgrade to version 2.5.19
- 5. Alternatively, you can manually upload version 2.5.19 of the plugin from the WordPress repository
- 6. After updating, verify the plugin version shows 2.5.19 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Most And Least Read Posts Widget
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49628 — 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-2024-49628 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