dbcve.org
Albo Pretorio OnlineWordPress extension · Eduva

CVE-2023-32109

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-18
Fix available
A fix is available. Upgrade to after 4.6.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Ignazio Scimone Albo Pretorio On line plugin <= 4.6.3 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 confidence

Unauthenticated reflected Cross-Site Scripting (XSS) vulnerability in the Albo Pretorio On line WordPress plugin by Ignazio Scimone allows attackers to inject malicious JavaScript via unsanitized input parameters in versions 4.6.3 and below.

MitigationUpdate the Albo Pretorio On line plugin to the latest version beyond 4.6.3. If no update is available, remove or disable the plugin until a patched version is released.

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
Albo Pretorio OnlineWordPress extension
Affected:<= 4.6.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Albo Pretorio On line plugin files
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'albo-pretorio-on-line' or similar variant containing 'albo pretorio' in the name
    Affected if The plugin folder is present on the server
  2. Identify the installed plugin version
    Open the main plugin file (usually albo-pretorio-on-line.php) and locate the version header comment at the top, or check the WordPress admin under Plugins > Installed Plugins
    Affected if The reported version is 4.6.3 or lower (any version <= 4.6.3)
  3. Confirm the plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to verify the Albo Pretorio On line plugin is activated, or query the wp_options table for option_name = 'active_plugins'
    Affected if The plugin appears in the list of active plugins and the version is <= 4.6.3
  4. Verify the plugin author
    Confirm the plugin author is 'Ignazio Scimone' to ensure you are checking the correct vulnerable plugin, as other similar-named plugins may exist
    Affected if The author matches 'Ignazio Scimone' and version is <= 4.6.3

If the Albo Pretorio On line plugin by Ignazio Scimone is installed, active, and the installed version is 4.6.3 or lower, the environment is affected by this reflected XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 4.6.3
Interim mitigation

Update the Albo Pretorio On line plugin to the latest version beyond 4.6.3. If no update is available, remove or disable the plugin until a patched version is released.

Recommended fix Moderate confidence

Albo Pretorio Online 4.6.4 or later

  1. 1. Check the official WordPress plugin repository or vendor website for the Albo Pretorio Online plugin
  2. 2. Verify if version 4.6.4 or a later version is available as the fixed release
  3. 3. Before upgrading on production, test the fixed version in a staging environment
  4. 4. Create a full backup of the WordPress site and database
  5. 5. Upgrade the Albo Pretorio Online plugin to the latest fixed version
  6. 6. Verify the XSS vulnerability is resolved by testing the affected parameter
  7. 7. Confirm other site functionality remains intact after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Albo Pretorio Online Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32109 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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