Agp Font Awesome CollectionWordPress extension · Profosbox
CVE-2023-30481
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) 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 · high confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the AGP Font Awesome Collection WordPress plugin versions 3.2.4 and below. The vulnerability allows an attacker to inject malicious JavaScript through unsanitized user input that gets reflected back in the web page, potentially stealing session cookies or performing actions on behalf of authenticated users.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Locate the AGP Font Awesome Collection plugin filesCheck the wp-content/plugins/ directory for a folder named 'agp-font-awesome-collection' or similar. Look for the main plugin PHP file and inspect the plugin header comment for the Version field.Affected if The plugin folder exists and the Version header shows 3.2.4 or lower.
-
Check the plugin version from WordPress adminNavigate to WordPress Dashboard > Plugins > Installed Plugins. Locate 'AGP Font Awesome Collection' in the plugin list and read the version number displayed beneath the plugin name.Affected if The displayed version is 3.2.4 or any version number lower than 3.2.4.
-
Verify plugin version via readme.txtIf accessing the filesystem, open the plugin directory and locate the readme.txt file. Look for the 'Stable tag' entry in the file header.Affected if The Stable tag indicates version 3.2.4 or below.
-
Confirm the plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that the AGP Font Awesome Collection plugin shows as 'Active' rather than 'Inactive'.Affected if The plugin is active and the version is 3.2.4 or lower, making the reflected XSS accessible to unauthenticated attackers.
You are affected if the AGP Font Awesome Collection plugin is installed, active, and the installed version is 3.2.4 or lower, as this allows unauthenticated attackers to inject malicious JavaScript through unsanitized reflected parameters.
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 dataUpgrade the AGP Font Awesome Collection plugin to a version newer than 3.2.4, or apply vendor-supplied patch. If no update available, implement output encoding and input validation on plugin endpoints using WordPress sanitization functions (esc_html, esc_attr, sanitize_text_field).
Fix this in Agp Font Awesome Collection
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-2023-30481 — 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-30481 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