CVE-2023-47656
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 · uneditedAuth. (editor+) Stored Cross-Site Scripting (XSS) vulnerability in Marco Milesi ANAC XML Bandi di Gara plugin <= 7.5 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 confidenceAuthenticated (editor+) stored cross-site scripting vulnerability in the Marco Milesi ANAC XML Bandi di Gara WordPress plugin. The plugin fails to properly sanitize user input, allowing an attacker with editor-level privileges to inject malicious JavaScript that persists and executes when other users view the affected content.
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<= 7.5CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm plugin is installedLocate the Marco Milesi ANAC XML Bandi di Gara plugin in your WordPress installation's plugin directory. Use WP CLI command: wp plugin list --search='*anac*' or manually inspect the /wp-content/plugins/ directory for folders containing 'anac' or 'marcomilesi'.Affected if The plugin is present in the WordPress environment.
-
Identify installed versionOpen the main plugin PHP file and locate the Version header in the plugin comment block, or check the readme.txt file within the plugin folder. Alternatively, use WP CLI: wp plugin get marcomilesi-anac-xml-bandi-di-gara --field=versionAffected if The version number is 7.5 or lower.
-
Verify plugin is activeCheck if the plugin is currently activated. Use WP CLI: wp plugin status marcomilesi-anac-xml-bandi-di-gara, or log into WordPress admin and navigate to Plugins > Installed Plugins to confirm the plugin shows as 'Active'.Affected if The plugin is active and running.
-
Check for stored XSS payloadsInspect the plugin's settings pages and any database entries where plugin data is stored. Examine the wp_options table for rows related to the plugin (option_name containing 'anac' or 'marcomilesi'), or use WP CLI to export plugin settings: wp option list --search='%anac%'. Review any stored values for suspicious HTML script tags, javascript: URIs, or event handler attributes.Affected if Malicious script content is found stored in plugin options or related database entries.
You are affected if the Marco Milesi ANAC XML Bandi di Gara plugin is installed at version 7.5 or below and is currently active.
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 ANAC XML Bandi di Gara plugin to version 7.6 or later. If no update is available, disable or remove the plugin until a patched version is released.
- Consultation2.0 h
- Implementation4.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47656 — 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-47656 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