Post Pay CounterWordPress extension · Post Pay Counter Project
CVE-2017-18584
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 · uneditedThe post-pay-counter plugin before 2.731 for WordPress has no permissions check for an update-settinga action.
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 confidenceThe post-pay-counter WordPress plugin before version 2.731 lacks proper capability/permission checks on an update-settings AJAX action, allowing unauthenticated or lower-privileged users to modify plugin settings without authentication.
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
Post Pay CounterWordPress extension
< 2.731CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 Post Pay Counter plugin is installedCheck your WordPress plugins directory or use wp-cli: wp plugin list --status=active --format=csv | grep -i 'post pay counter'Affected if The plugin is installed and active
-
Check the installed plugin versionView the plugin header in wp-content/plugins/post-pay-counter/post-pay-counter.php or use: wp plugin get post-pay-counter --format=jsonAffected if Version is less than 2.731 (e.g., 2.7, 2.72, 2.730)
-
Verify the update-settings AJAX action is exposedInspect the plugin PHP file for AJAX action registration: look for 'add_action("wp_ajax_nopriv_update-settings"' or similar nopriv AJAX handlers that lack capability checksAffected if The AJAX action is registered with nopriv capability allowing unauthenticated access
-
Test AJAX endpoint accessibilitySend a POST request to /wp-admin/admin-ajax.php with action=update-settings and observe if the server accepts it without requiring authenticationAffected if The endpoint responds without requiring login (HTTP 200 instead of 401/403)
-
Review plugin settings for unauthorized changesCheck the WordPress database table wp_options for option_name containing 'ppc' or 'post_pay_counter' and inspect values for unexpected modificationsAffected if Settings appear modified but no admin user account was used to change them
You are affected if the Post Pay Counter plugin version is below 2.731 and the update-settings AJAX action accepts requests without authentication.
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 data2.731
Update the post-pay-counter plugin to version 2.731 or later, which includes proper permission checks on the update-settings action.
Fix this in Post Pay Counter
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18584 — 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-2017-18584 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