Skip to content
Noroxi
CVE-2014-3900· NVD / CVE Program· CNA jpcert

Cross-site scripting (XSS) vulnerability in admin/picture_modify.php in the photo-edit subsystem in Piwigo 2.6.3 and earlier allows remote a

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 77.7% of all records.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Cross-site scripting (XSS) vulnerability in admin/picture_modify.php in the photo-edit subsystem in Piwigo 2.6.3 and earlier allows remote attackers to inject arbitrary web script or HTML via the associate[] field, a different vulnerability than CVE-2014-4649.

MediumCVSS 4.3 · v2.0—No exploit No fix recorded
Published
Aug 17, 2014
Updated
Jun 16, 2026
EPSS
1.8% · 78th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2014-3900

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
piwigopiwigo

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • piwigo piwigoup to 2.6.3 inclusive
  • piwigo piwigo2.6.0
  • piwigo piwigo2.6.1
  • piwigo piwigo2.6.2

Other highest-scoring records for the same primary product.

  • CVE-2020-19213SQL Injection vulnerability in cat_move.php in piwigo v2.9.5, via the selection parameter to move_categories.
    44Plan
  • CVE-2023-33362Piwigo 13.6.0 is vulnerable to SQL Injection via in the "profile" function.
    42Plan
  • CVE-2017-10682SQL injection vulnerability in the administrative backend in Piwigo through 2.9.1 allows remote users to execute arbitrary SQL commands via
    41Plan
  • CVE-2021-32615Piwigo 11.4.0 allows admin/user_list_backend.php order[0][dir] SQL Injection.
    40Plan
  • CVE-2016-10105admin/plugin.php in Piwigo through 2.8.3 doesn't validate the sections variable while using it to include files.
    40Plan
  • CVE-2014-4648Unspecified vulnerability in Piwigo before 2.6.3 has unknown impact and attack vectors, related to a "security failure."
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    P · data or configuration can be modified
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    P
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:N/I:P/A:N

    nvd-primary

    Root cause

    User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    commentEl.innerHTML = comment.body;

    Fixed

    ts
    commentEl.textContent = comment.body;

    Change log

    No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

    References

    Show all references (3 more)

    Vendor advisories and official records. Exploit/PoC links are deliberately left out.

    All records