Agp Font Awesome CollectionWordPress extension · Profosbox
CVE-2023-45749
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 Alexey Golubnichenko AGP Font Awesome Collection plugin <= 3.2.4 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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in the AGP Font Awesome Collection WordPress plugin versions 3.2.4 and below. The vulnerability allows remote attackers to trick authenticated administrators into performing unintended actions via maliciously crafted requests, likely due to missing or improper nonce token validation in plugin admin functions.
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
Agp Font Awesome CollectionWordPress extension
<= 3.2.4CVSS 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 AGP Font Awesome Collection plugin filesNavigate to your WordPress installation wp-content/plugins/ directory and look for a folder named 'agp-font-awesome-collection' or similar. Also check via the WordPress admin dashboard under Plugins > Installed Plugins.Affected if The plugin folder exists and the plugin is installed on the WordPress site.
-
Identify the installed plugin versionOpen the main plugin PHP file (typically agp-font-awesome-collection.php) and look for the version number in the plugin header comment at the top of the file, or check the readme.txt file for the 'Stable tag' entry.Affected if The version listed is 3.2.4 or any version lower than 3.2.4.
-
Verify the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and confirm whether the AGP Font Awesome Collection plugin shows as 'Active'.Affected if The plugin is active and running in a production or accessible WordPress environment.
-
Check for admin access exposureDetermine if the WordPress site allows administrator-level access, as CSRF attacks targeting this vulnerability require tricking authenticated administrators. Review user roles with administrator capabilities.Affected if Administrator accounts exist and can access the WordPress admin dashboard where the plugin settings are exposed.
A user is affected if the AGP Font Awesome Collection plugin version 3.2.4 or lower is installed and active on a WordPress site with administrator accounts, since the CSRF flaw can be exploited via maliciously crafted requests to admin functions lacking proper nonce validation.
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 AGP Font Awesome Collection plugin to a version newer than 3.2.4. If no patched version is available, disable the plugin until a fix is released.
Fix this in Agp Font Awesome Collection
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-2023-45749 — 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-45749 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