About MeWordPress extension · About Me Project
CVE-2022-36387
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 · uneditedBroken Access Control vulnerability in Alessio Caiazza's About Me plugin <= 1.0.12 at WordPress.
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 confidenceBroken Access Control vulnerability in Alessio Caiazza's About Me WordPress plugin versions 1.0.12 and below allows unauthorized users to access sensitive information or functionality they should not have permission to access. The CVSS 9.8 indicates network-exploitable, no privileges required, and no user interaction needed.
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
About MeWordPress extension
<= 1.0.12CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Verify About Me plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, or check the wp-content/plugins/ directory for a folder named 'about-me' or similarAffected if The About Me plugin by Alessio Caiazza appears in the installed plugins list
-
Identify the installed versionIn WordPress admin, find the About Me plugin in the plugins list and locate the version number displayed under the plugin name, or read the main plugin file header in wp-content/plugins/Affected if The displayed version number is 1.0.12 or lower
-
Confirm the plugin authorVerify the plugin author is Alessio Caiazza (or nicolus, which is the WordPress.org username) to ensure you are checking the correct pluginAffected if The author matches Alessio Caiazza and the version is 1.0.12 or below
If the About Me plugin by Alessio Caiazza is installed at version 1.0.12 or lower, the environment is affected by this Broken Access Control vulnerability.
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.
dbcve · scopedUpdate the About Me plugin to a version newer than 1.0.12 that includes proper authorization checks, or remove the plugin if no patched version is available.
Latest version available on wordpress.org (greater than 1.0.12)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'About Me' plugin by Alessio Caiazza
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Verify the update was successful by checking the plugin version
- 6. If no update is available in the WordPress admin, visit the plugin's page at wordpress.org/plugins/about-me/ to download the latest version manually
- 7. Deactivate and delete the current version, then upload and activate the new version
- 8. Test the plugin functionality to ensure it works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in About Me
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36387 — 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-2022-36387 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