Enhanced Plugin AdminWordPress extension · Infolific
CVE-2023-28618
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 Marios Alexandrou Enhanced Plugin Admin plugin <= 1.16 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Marios Alexandrou Enhanced Plugin Admin WordPress plugin affecting versions 1.16 and below. The flaw allows remote attackers to trick authenticated administrators into performing unintended administrative actions via maliciously crafted 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
Enhanced Plugin AdminWordPress extension
<= 1.16CVSS 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.
-
Check if Enhanced Plugin Admin plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'Enhanced Plugin Admin' or 'Marios Alexandrou'. Alternatively, check the plugin directory /wp-content/plugins/ for a folder containing 'enhanced-plugin-admin' or check via WP-CLI: wp plugin list --search='*enhanced*'Affected if The plugin appears in the installed plugins list
-
Identify the installed version numberIn WordPress admin > Plugins, find the Enhanced Plugin Admin plugin and look at the version number displayed below the plugin name. Alternatively, open the main plugin PHP file (usually enhanced-plugin-admin.php or similar in the plugin folder) and locate the 'Version:' header commentAffected if Version is 1.16 or lower (or if no version is displayed and the plugin is present)
-
Confirm the plugin author matches the CVEVerify the plugin author is 'Marios Alexandrou' or 'Infolific' by checking the plugin details in WordPress admin or the author field in the plugin headerAffected if Author is Marios Alexandrou or Infolific and version is 1.16 or below
-
Verify plugin is activeIn WordPress admin > Plugins, check if Enhanced Plugin Admin shows as 'Active'. Alternatively, use WP-CLI: wp plugin is-active enhanced-plugin-admin (adjust folder name as needed)Affected if Plugin is active and version is 1.16 or below
You are affected if the Enhanced Plugin Admin plugin by Marios Alexandrou or Infolific is installed, active, and the installed version is 1.16 or lower.
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 dataUpdate the plugin to a version beyond 1.16 that implements anti-CSRF tokens, or manually add token validation to all state-changing form actions and AJAX endpoints within the plugin.
Fix this in Enhanced Plugin Admin
Scoped from the published advisory
- Consultation2.0 h
- Implementation5.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 $3,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28618 — 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-28618 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