Post Pay CounterWordPress extension · Post Pay Counter Project
CVE-2017-18583
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 PHP Object Injection.
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 confidenceThe post-pay-counter WordPress plugin before version 2.731 is vulnerable to PHP Object Injection via unsafe deserialization of untrusted input. This vulnerability can be exploited to achieve remote code execution, authentication bypass, or file manipulation through the injection of malicious PHP objects.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 Post Pay Counter plugin filesCheck the wp-content/plugins/ directory for a folder named 'post-pay-counter' or similar. Also check wp-content/plugins/post-pay-counter/ for the main plugin file.Affected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed plugin versionOpen the main plugin PHP file (usually post-pay-counter.php) and locate the version in the plugin header comment, or check the readme.txt file for the 'Stable tag' entry.Affected if Version number is less than 2.731 or cannot be determined
-
Verify the vulnerability conditionCompare the identified version against the affected range: any version below 2.731 is vulnerable.Affected if Installed version is below 2.731
If the Post Pay Counter plugin is installed with a version lower than 2.731, the environment is affected by this PHP Object Injection vulnerability.
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.731
Update the post-pay-counter plugin to version 2.731 or later to remediate the vulnerability.
Post Pay Counter version 2.731
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find 'Post Pay Counter' in the plugin list
- Click 'Update now' if an update is available, or manually update to version 2.731 or later
- Verify the plugin updated successfully
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Post Pay Counter
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18583 — 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-18583 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